apprunner-roadmap
apprunner-roadmap copied to clipboard
Specify DNS record type explicitly
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 Please specify DNS record type as "CNAME" explicitly in the description below.
Typically, TXT record is used for DNS validation. So people can misunderstand that App Runner provides TXT records but actually they are CNAME records.
Some people who're familiar with AWS Certificate Manager might be able to understand they are CNAME records not TXT records (ACM uses CNAME for the validation). Also the official docs says:
When you associate a custom domain with your service, App Runner provides you with a set of CNAME records to add to your Domain Name System (DNS).
https://docs.aws.amazon.com/apprunner/latest/dg/manage-custom-domains.html
But specifying them explicitly in App Runner Console is more user-friendly for everyone.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Adding a new column "Record Type" in addition to the "Record Name" and "Value".
Additional context Anything else we should know?
An App Runner user told me that they got stuck in the issue before. They were confused about the DNS record type.
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.)
N/A
I use cloudflare as a DNS Provider, and as per their documentation the validation records are TXT records. This is such a simple suggestion that would have saved me two days of waiting for domain validation, then I used the CNAME type as suggested by spesnova then everything worked fine.
Have to agree, kind of low-hanging fruit here.
this problem has troubled me for a long time. I used the CNAME now, waiting for verification result hope everything is fine
It is slightly concerning to see such a simple issue going stale after almost a year. It‘s an obvious UX improvement, with zero risk involved, basically a documentation fix.
This is still an issue in 2023. At least this Github issue comes up when you google the problem which is what prevented me from hours of headaches.
Super simple to fix issues like this that are still hanging around, and no visible interaction from the app runner team is the reason I've decided not to use this service. This kind of low standard shouldn't be permitted by AWS.
It looks like this has been completed.
@wub
Thanks for letting us know.