[ECS] [Fargate][Bug]: target group ignores custom port
Open
ECS
Fargate
Proposed
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
An annoying bug, when setting up a service there is an option for a new target group which defaults to port 80. Entering a different value here doesn't translate to the value being used which continues to be 80.
A workaround is to create the target group and ELB in VPC prior to creating the service and attaching at that point.
Contributor guide
Research direction
Start by reproducing the ECS/Fargate service setup described in the issue: create a target group with a custom port and attach it during service creation. Compare the configured port with the port used by the resulting target group attachment; done means the entered custom port is retained instead of defaulting to 80.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100