[ECS] [AWS CloudMap [request]: Use an existing hosted zone for the CloudMap namespace when using service discovery

[jenademoodley]

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 When creating a namespace, CloudMap automatically creates a new private/public hosted zone for the records. This feature request is to allow the use of an existing hosted zone for the CloudMap (i.e. service discovery) records.

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? There is an existing hosted zone used for inter-service communication using a bunch of public load balancers, and application knows about these load-balancer entries via the route53 zone. With current behaviour of creating a separate zone, the application would need to be updated to look at 2 zones.

It would also be useful to have records use an existing zone where a common domain would be used for services outside of CloudMap and ECS

[clown319]

I have no right to create new hosted zone in compony because security cause, so I hope this issue can be resolved.

[AdamDrewsTR]

Same issue here. We have existing hosted zones to deploy to, and we are unable to create our own. Being able to reference an existing one would solve this.

[JustasStarred]

Same issue, but with the addition of needing to associate multiple VPCs with the HostedZone created by CloudMap through CloudFormation. In CF, CloudMap does not support adding multiple VPCs, while HostedZones do therefore being able to use an existing HostedZone would provide a workaround.