- Newest
- Most votes
- Most comments
When an App Runner custom domain gets stuck in "PENDING_CERTIFICATE_DNS_VALIDATION" status despite having the correct CNAME records set up, there are several potential causes and solutions to consider:
-
DNS Propagation Delay: DNS changes can take time to propagate globally, sometimes up to 48-72 hours. Since you're using Cloudflare, ensure that the records have fully propagated.
-
Cloudflare Configuration: While you've mentioned your CNAMEs are set to DNS-only (no proxy) which is correct, sometimes Cloudflare can still modify DNS records in ways that affect validation. Verify that Cloudflare isn't making any modifications to your CNAME records.
-
CAA Records: Check if there are any Certificate Authority Authorization (CAA) records for your domain. At least one CAA record should include "amazon.com" to allow AWS to issue certificates for your domain.
-
Certificate Validation Timeout: ACM certificate validation typically times out after 72 hours. If this has happened, you'll need to:
- Disassociate (unlink) the custom domain from your App Runner service
- Clean up any conflicting DNS records
- Re-associate (link) the custom domain with your App Runner service
- Add the new certificate validation CNAME records to Cloudflare
- CNAME Conflicts: Ensure there are no conflicting records for the same domain/subdomain pointing elsewhere.
Unfortunately, there's no direct way to "force revalidation" of an ACM certificate. The best approach is to delete the current association and start fresh:
- Remove the custom domain from your App Runner service
- Wait a few minutes for the system to clean up
- Add the custom domain again to your App Runner service
- Promptly add the new CNAME validation records to Cloudflare
- Ensure the records are properly configured (DNS-only, no proxy)
If the problem persists after following these steps, you may need to contact AWS Support for further assistance with your specific configuration.
Sources
AWS Apprunner custom domain linking issue | AWS re:Post
ACM certificate stuck in “Pending validation” despite correct DNS CNAMEs | AWS re:Post
Timeout when creating custom domain on AWS amplify | AWS re:Post
Unable to request a Certificate in AWS | AWS re:Post
Hello.
I tried to resolve the CNAME record you provided in my environment, but was unable to do so.
dig cname _46a5503a7902e4cd580274c1594bba.api.kalshiwxbridge.com
; <<>> DiG 9.18.39-0ubuntu0.24.04.2-Ubuntu <<>> cname _46a5503a7902e4cd580274c1594bba.api.kalshiwxbridge.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49669
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;_46a5503a7902e4cd580274c1594bba.api.kalshiwxbridge.com. IN CNAME
;; AUTHORITY SECTION:
kalshiwxbridge.com. 1737 IN SOA eloise.ns.cloudflare.com. dns.cloudflare.com. 2387520933 10000 2400 604800 1800
;; Query time: 36 msec
;; SERVER: 10.255.255.254#53(10.255.255.254) (UDP)
;; WHEN: Sun Nov 02 09:23:07 JST 2025
;; MSG SIZE rcvd: 144
dig cname _a71b9e2e21bc56bc1f5da1f09f84d7f.api.kalshiwxbridge.com
; <<>> DiG 9.18.39-0ubuntu0.24.04.2-Ubuntu <<>> cname _a71b9e2e21bc56bc1f5da1f09f84d7f.api.kalshiwxbridge.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44980
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;_a71b9e2e21bc56bc1f5da1f09f84d7f.api.kalshiwxbridge.com. IN CNAME
;; AUTHORITY SECTION:
kalshiwxbridge.com. 1800 IN SOA eloise.ns.cloudflare.com. dns.cloudflare.com. 2387520933 10000 2400 604800 1800
;; Query time: 45 msec
;; SERVER: 10.255.255.254#53(10.255.255.254) (UDP)
;; WHEN: Sun Nov 02 09:23:35 JST 2025
;; MSG SIZE rcvd: 145
I also tried checking the DNS propagation on the following website, but name resolution failed in every region.
https://whatsmydns.me/#CNAME/_46a5503a7902e4cd580274c1594bba.api.kalshiwxbridge.com
https://whatsmydns.me/#CNAME/_a71b9e2e21bc56bc1f5da1f09f84d7f.api.kalshiwxbridge.com
Have you added the CNAME record correctly on the Cloudflare screen?
Did you turn off the proxy setting when adding the Cloudflare record?
I've seen cases in the past where this setting was enabled and CNAME records failed to validate.
Also, it is possible that the CAA record is the problem, so please check the CAA record as described in the reddit post below.
https://www.reddit.com/r/aws/comments/1jwitlq/aws_acm_cloudflare_certificate_validation_kept/?tl=ja
Both validation CNAMEs now resolve publicly from Cloudflare (DNS-only, DNSSEC disabled).
dig +short CNAME _46a5503a7902e4cd580274c1594bba.api.kalshiwxbridge.com → _deb909fde9394606d917a1c15a210b7f.jkddzztszm.acm-validations.aws.
dig +short CNAME _a71b9e2e21bc56bc1f5dfa19f0f84f7df.api.kalshiwxbridge.com → _244765d23423ab196790757b38edf27d.jkddzztszm.acm-validations.aws.
Please retry or force revalidation for: App Runner custom domain api.kalshiwxbridge.com (service wx-kalshi-bridge-v5, region us-east-1).
answered a year ago
Relevant content
asked 2 years ago
asked 5 years ago
