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
Currently, linking a custom domain to an App Runner service requires CNAME record validation from an internet facing domain. With the introduction of App Runner Private Services, there is now a valid use-case for internal facing App Runner services to use a custom domain from a private Route53 Hosted Zone.
Describe alternatives you've considered
The current alternatives are using a public facing custom domain to link to a private App Runner service, or using another AWS service such as Elastic Beanstalk.
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.)
Community Note
Tell us about your request Currently, linking a custom domain to an App Runner service requires CNAME record validation from an internet facing domain. With the introduction of App Runner Private Services, there is now a valid use-case for internal facing App Runner services to use a custom domain from a private Route53 Hosted Zone.
Describe alternatives you've considered The current alternatives are using a public facing custom domain to link to a private App Runner service, or using another AWS service such as Elastic Beanstalk.
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.)