I'm dealing with a situation where I need some help getting my ACM certificate out of a pending state. I have an application that's running in the us-west-2 region, but it has a strange bug that disappears when I run it in us-west-1. To temporarily fix the issue, I want to redirect the domain to the new region while I figure out the underlying bug.
In the original setup using ACM and Route 53 with DNS validation, everything worked fine. However, for the new certificate in us-west-1, I've followed the same process, and it just won't validate. I've already tried deleting and re-adding the CNAME record from the hosted zone for the new region.
Could there be a conflict with the original instance that's preventing the certificate from validating? Thanks for any help!
1 Answer
It sounds like you're on the right track, but make sure that when you set up the CNAME records for your certificate, they match exactly with what the ACM wizard provided. Have you validated those records using dig or any DNS tool? And by the way, what is the bug in your app? It might be easier to troubleshoot if we know more about it!
That’s tricky! It sounds like you’ve narrowed it down, especially since it works in a different region. I can understand the urgency to get back online and fix things later. You mentioned that the client app has a hardcoded URL—did you consider using a temporary redirect or something while you solve the main issue?
I did follow the ACM wizard's instructions when creating the CNAME records, and they match. The bug seems to occur during the creation of a Google Sheet at the end of my data processing, but it fails without throwing any errors. It happens in production only, while the exact same code runs fine in development.