[service] [request]: ECS Service Discovery IPv6
- 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**
Add IPv6 dns resolution of Service Discovery using Route 53.
**Which service(s) is this request for?**
Fargate, ECS, Route 53
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
When our ECS fargate containers do DNS resolution they get results from A record, but they wait on the AAAA records to timeout as IPv6 is preferred in ubuntu. This is causing random extra times on internal requests.
**Are you currently working around this issue?**
Having to either turn off ipv6 for the VPC or deal with the timeouts.
Contributor guide
Research direction
Issue 1331 names ECS, Fargate, and Route 53 but no repository files, tests, or implementation entry points. Start by researching ECS Service Discovery DNS behavior for IPv6 and AAAA records. Done means Service Discovery supports IPv6 DNS resolution without the reported AAAA lookup timeouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100