aws / aws/containers-roadmap

[ECS] [Fargate]: bug in creation of Task Definition with not acceptable portMappings via AWS Console

Open
#1,776 1 comment 0 reactions 1 assignee Claimed by @genbit View on GitHub
ECS Fargate Issue/Bug
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
There is a bug within the [AWS Task Definition](https://us-east-1.console.aws.amazon.com/ecs/home?region=us-east-1#/taskDefinitions) creation console which can be described as follows:

1. Create a Fargate ECS task with portMappings as shown below:

```
"portMappings": [
{
"hostPort": 8080,
"protocol": "tcp",
"containerPort": 80
}
],
```

2. Press "Create"
3. A message will be presented that looks as follows: `Created new revision of Task Definition nginx:51 successfully`.
4. Reopen the new task and the Port Mappings will be shown as follows:
```
"portMappings": [
{
"hostPort": 80,
"protocol": "tcp",
"containerPort": 80
}
],
```

I don't believe this is possible, btw, but the user-interface allows the creation of the configuration above.

**Which service(s) is this request for?**
ECS Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

I'm hoping to provide a bug-free experience for users of the ECS Fargate offering who are utilizing the AWS Console to create (or test) ECS Fargate services.

**Are you currently working around this issue?**
We render all of our Task Definitions via CloudFormation/terraform, but there is no workaround for this bug. You enter data one way AWS changes it rather than throws an error.

**Additional context**
There are two files attached to show the bug:

1. Before - Creating nginx-53.png
2. After - Viewing nginx-53.png

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look.
(Remember to remove any personally-identifiable information.)

Before Image - Creation of a New Task Definition
Before - Creating nginx-53

After Image - Viewing The Task Definition
After - Viewing nginx-53

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.