[ECS] [request]: Service Discovery with Public IP

<!--- Please keep this note for the community ---> ### 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 <!--- Thank you for keeping this note for the community ---> **Tell us about your request** Support for public DNS resolving to public ip with Service Discovery. **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?** To reduce the maintenance burden, I'm trying to replace an EC2 that acts as a bastion for the VPC with a Fargate Container. However, the only way to have a reliable DNS is using a Network Load Balancer in front of the container. We run this setup on 4 different regions, which means we'd end up paying for 4 NLB with almost no gain. The alternative is to have a DNS that resolves to the container and gets automatically updated much like the ServiceDiscovery for private DNS. **Are you currently working around this issue?** We're currently running a sidecar container with AWS CLI that updates Route 53 with the public ip that was designated to th

Posted by deleugpn on Feb 5, 2020, 5:53 PM

Tags

• support (Network)

Related issues

• That Reddit post is feeding more conspiracy thinking than helping.
• Support BYOK/Custom Models for Inline Code Completions
• DNS-PERSIST-01 challenge support (planned for late Q1 2026)
• Yeah I can't really blame people for not realising they have shitty mics and shitty internet because it's really hard for them to tell!
• Onboarding guide for FluentAssertions
• Add WebTransport support