aws / aws/containers-roadmap

[ECS] [AWS CloudMap]: Increase number of records returned by Route53 for cloudmap entries

Open
#1,231 1 comment 23 reactions 0 assignees View on GitHub
ECS Proposed
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**
When using Cloudmap the SRV and A records return only a maximum of 8 records at a time, for applications like HAproxy where you may want to get a list of all containers running application X so that you can load balance them, returning only 8 records means that the applications thrash their pools pulling servers in and out of rotation. Service discovery tools such as consul etc don't impose this limitation. And yes ALBs can be used but they definitely don't provide the same flexibility as HAproxy in this regard.

**Which service(s) is this request for?**
Fargate, Cloudmap

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Return more than 8 records for SRV or A records when using cloudmap, ideally 100+
**Are you currently working around this issue?**
It's a current deal breaker for ECS service discovery..

Contributor guide

Open the contributing guide

Research direction

Start with issue #1231 and its description of the Fargate and CloudMap service-discovery behavior. Confirm the current SRV and A record limit and determine whether the requested increase is possible within the affected AWS services. Done means CloudMap can return more than eight records, ideally 100 or more, without the reported pool thrashing.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.