Community Note

• Please vote on this issue by adding a 👍 reaction 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
What do you want us to build?
Support ECS calls to external AWS service endpoints over IPv6 on dual-stack instances in addition to IPv6-only instances to avoid the need for IPv4 networking.

Which service(s) is this request for?
ECS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
ECS dependencies like the ECS Agent are gaining support for calling AWS service endpoints (ECS, ECR, S3, etc.) over their dual-stack endpoints on IPv6-only instances. I think there would be value in enabling dual-stack ECS instances to use those dual-stack AWS service endpoints as well, ideal for cases where an application still needs to support IPv4 in some capacity (e.g., inbound requests to those ECS instances, networking with an AWS service that doesn't yet support IPv6) but could stand to save costs on NAT Gateways and/or VPC Endpoints by having outbound connectivity to ECS utilities be over IPv6 whenever possible.

Are you currently working around this issue?
How are you currently solving this problem?
I can configure AWS SDKs in my own applications to use the dual-stack endpoints (where possible), but the ECS instance wouldn't be able to orchestrate tasks or pull images from ECR without a NAT Gateway or VPC Endpoints.

Additional context
Anything else we should know?

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.)