(certificatemanager): DnsValidatedCertificate timeout while waiting for certificate approval
See original GitHub issueDescribe the bug Creating certificates via certificate manager and route54 DNS validation fails with a timeout. Error message:
Failed to create resource. Resource is not in the state certificateValidated
Expected behavior The lambda waiting for the approval should probably wait more than the hardcoded 5 minutes right now.
Version:
- OS: linux
- Programming Language: typescript
- CDK Version: 0.33.x
Issue Analytics
- State:
- Created 4 years ago
- Reactions:28
- Comments:33 (7 by maintainers)
Top Results From Across the Web
class DnsValidatedCertificate (construct) · AWS CDK
A certificate managed by AWS Certificate Manager. Will be automatically validated using DNS validation against the specified Route 53 hosted zone.
Read more >No matter what I do, I cannot seem to get CDK to create and ...
No matter what I do, I cannot seem to get CDK to create and DNS validate a certificate (pending/timeout) · do the three...
Read more >CDK DnsValidatedCertificate: Can create a certificate in a ...
Go look up the request in Amazon Certificate Manager of the linked ... You can tweak the permission sets in each account to...
Read more >aws_acm_certificate_validation | Resources | hashicorp/aws
This resource represents a successful validation of an ACM certificate in concert with ... and aws_acm_certificate to request a DNS validated certificate, ...
Read more >@aws-cdk/aws-certificatemanager | Yarn - Package Manager
AWS Certificate Manager (ACM) handles the complexity of creating, storing, and renewing public and private SSL/TLS X.509 certificates and keys that protect ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had this same issue happen, and it turned out that my domain had a different set of name servers than the created hosted zone.
To fix it manually: You can update the name servers for a domain to match the hosted zone in the top right of the domain information on the R53 console (on the left menu click on “registered domains” then click on your domain in the list).
AWS docs for updating name servers here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
As for the CDK, the HostedZone construct should probably be updated to use the name servers that the domain is configured for so that multiple hosted zones can be created for the same domain.
It is also worth noting that I had transferred the domain from a different AWS account, and had no existing hosted zones. Not sure how the existing implementation determines what name servers to use for a hosted zone, but maybe this is why it is failing to use the correct ones?
Still a problem; Requested at 2020-01-16T10:33:04UTC Issued at 2020-01-16T10:46:21UTC Can the delay duration be a variable so we can specify a value?