[Fargate/ECS/NLB] [request]: ECS Fargate NLB UDP container support in AWS CDK
- 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**
ECS Fargate NLB UDP container support in AWS CDK
**Which service(s) is this request for?**
ECS, Fargate, NLB
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Got ECS Fargate service with NLB configured without problems with management console, but unable to do the same with AWS CDK stack. CDK seems to register container port of first container of the sevice to NLB and won't let define it as UDP, but only TCP is allowed? Not sure if this is right place to ask, bit is it so, that CDK is not yet supprting UDP containers with NLB and if so is that in roadmap?
**Are you currently working around this issue?**
No
Contributor guide
Research direction
Start by reproducing the ECS Fargate service and NLB configuration in an AWS CDK stack, comparing it with the management-console setup. Inspect how the CDK selects the first container port and permits TCP versus UDP. Done means CDK can represent the requested UDP container/NLB configuration and the behavior is covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100