-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
certificatemanager.DnsValidatedCertificate has too low timeout #5835
Labels
@aws-cdk/aws-certificatemanager
Related to Amazon Certificate Manager
bug
This issue is a bug.
in-progress
This issue is being actively worked on.
p2
Comments
konstantinj
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Jan 16, 2020
SomayaB
added
the
@aws-cdk/aws-certificatemanager
Related to Amazon Certificate Manager
label
Jan 16, 2020
A solution would be to switch to the new custom resource provider framework. |
Duplicate of #5831. |
jogold
added a commit
to jogold/aws-cdk
that referenced
this issue
Jun 15, 2020
…icate Automatically adding Amazon Route 53 CNAME records for DNS validation is now natively supported by CloudFormation. Add a `validation` prop to `Certificate` to handle both email and DNS validation. Deprecate `DnsValidatedCertificate`. The default remains email validation (non-breaking). Closes aws#5831 Closes aws#5835 Closes aws#6081 Closes aws#6516 Closes aws#7150 Closes aws#7941 Closes aws#7995 Closes aws#7996
jogold
added a commit
to jogold/aws-cdk
that referenced
this issue
Jun 15, 2020
…cate Automatically adding Amazon Route 53 CNAME records for DNS validation is now natively supported by CloudFormation. Add a `validation` prop to `Certificate` to handle both email and DNS validation. Deprecate `DnsValidatedCertificate`. The default remains email validation (non-breaking). Closes aws#5831 Closes aws#5835 Closes aws#6081 Closes aws#6516 Closes aws#7150 Closes aws#7941 Closes aws#7995 Closes aws#7996
mergify bot
pushed a commit
that referenced
this issue
Jul 10, 2020
…cate (#8552) Automatically adding Amazon Route 53 CNAME records for DNS validation is now natively supported by CloudFormation. Add a `validation` prop to `Certificate` to handle both email and DNS validation. `DnsValidatedCertificate` is now only useful for cross-region certificate creation. The default remains email validation (non-breaking). Closes #5831 Closes #5835 Closes #6081 Closes #6516 Closes #7150 Closes #7941 Closes #7995 Closes #7996 Closes #8282 Closes #8659 Closes #8783 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-certificatemanager
Related to Amazon Certificate Manager
bug
This issue is a bug.
in-progress
This issue is being actively worked on.
p2
When creating a DnsValidatedCertificate currently in the us-east-1 region my stack creation fails due to not being able to validate the certificate in time. It's set to 15 minutes currently:
aws-cdk/packages/@aws-cdk/aws-certificatemanager/lib/dns-validated-certificate.ts
Line 65 in e3305d8
The AWS console reminds that it can take up to 30mins. Since DnsValidatedCertificate is creating a new certificate in a new stack all the time, it is (at least currently) not possible to create a stack with a DnsValidatedCertificate in us-east-1.
Reproduction Steps
Error Log
Environment
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: