Closed DavidWells closed 4 years ago
Hi, thanks for creating an issue!
The first thing I would try is creating the certificate manually and seeing if it validates after leaving it for a little longer that the resource allows - perhaps an hour.
Check if you can resolve the validation record yourself, e.g.:
$ dig _a98cbf......com
and see if you get the correct value back.
My guess is the zone delegation is not working. Check the NS record in the parent zone is correct.
Aha! I've figured it out.
My regions did not match. us-east-1
was set on the resource but the stack/API was in us-west-1
🙈.
So the custom resource did it's thing and continues to check for a non-existent recordset.
Closing this!
Thanks again for this awesome custom resource ❤️
Hey first off, many thanks for the awesome custom resource. It's super helpful!
It appears that everything is working correctly but I'm running into a timeout issue where the ACM cert gets stuck in a "pending validation" state.
Have you ever seen this before?
The CNAME was successfully created in Route53
And the custom resource lambda is doing its job (per its logs)
However, when the max execution time hits, the stack creation fails 😅
Any ideas on how I might be able to resolve this?
Many thanks!