aws
Unable to use the same custom domain on two services
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?
Here's our challenge: we have a production App Runner service that has the Custom Domain *.example.com. This uses the "build from code" build process. We need to change this to "build from ECR". We can't update the service in-place, so we have to create a new App Runner service. We can build the new service, but we can't add the domain name *.example.com to this new one.
How do we migrate from service A to service B with zero downtime? We were intending to get it set up and ready to receive requests, then simply re-route the DNS. This seems impossible without deleting service A - incurring downtime - then quickly adding the domain name to service B and praying ACM validates it quickly.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
No alternative available for reusing the same domain name when creating a new App Runner service.
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.)
