From 26bb450175f5b2d0ce1b4af75f3e9856dd414ef4 Mon Sep 17 00:00:00 2001 From: Simon-Pierre Gingras Date: Sat, 16 Mar 2019 05:48:44 -0700 Subject: [PATCH] chore(acm): update docs (#2028) Update class name in docs, remove outdated paragraph. --- packages/@aws-cdk/aws-certificatemanager/README.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/packages/@aws-cdk/aws-certificatemanager/README.md b/packages/@aws-cdk/aws-certificatemanager/README.md index 69889eb494533..0122b59e2b76b 100644 --- a/packages/@aws-cdk/aws-certificatemanager/README.md +++ b/packages/@aws-cdk/aws-certificatemanager/README.md @@ -5,7 +5,7 @@ can be used in CloudFront and ELB. ### DNS-validated certificates -The `DNSValidatedCertificateRequest` class provides a Custom Resource by which +The `DnsValidatedCertificateRequest` class provides a Custom Resource by which you can request a TLS certificate from AWS Certificate Manager that is automatically validated using a cryptographically secure DNS record. For this to work, there must be a Route 53 public zone that is responsible for serving @@ -44,9 +44,6 @@ in the email. The email addresses use will be: * postmaster@domain.com * webmaster@domain.com -DNS validation is possible in ACM, but is not currently available in CloudFormation. -A Custom Resource will be developed for this, but is not currently available. - Because of these blocks, it's probably better to provision your certificates either in a separate stack from your main service, or provision them manually. In both cases, you'll import the certificate into your stack afterwards.