I am trying to get an ACM Certificate through DNS verification. Orignally, when I created the request, it was denied within 5 minutes or so, and when I tried to figure out why, I thought maybe it was because the CNAMEs the cert. provided was not propagated yet. So I waited until 3rd party sources determined the CNAMEs were propagated. After several hours, I figured out I needed to make a new request, because my failed verficiation would not let me retest. I created a new ACM, and it was denied in less than 30 seconds, I didnt even have enough time to change my DNS settings with the possibly new DNS settings. I then decided to remove my current CNAMEs, and request a 3rd ACM. This time I had enough time to change and update the DNS, but ultimately, it resulted in a failure. My TTL was set to 300 (i dont know if that matters), but I am not sure what else I am supposed to do. The CNAMEs match perfectly, as they were copy and pasted.
I am hoping one of you is able to enlighten me and point me in the direction of a solution. The whole verification process is confusing to me, as I am unsure how I can be presented with a failure so quickly. My current understanding is that verification process is based on propagation, and if propagation can take up to 48 hours, why am I being denied in less than 5 minutes?
It may be beneficial to know that I am not using Route53, I am using a .com domain I purchased through hostinger, and I am not transfering it to AWS, I am just using it. Connecting my S3 to my DNS, to my knowledge, is working. However, I do have to use my S3 domain to access my page, and the purchased domain is currently inaccessible.
AWS OFFICIALUpdated 2 years ago
