AWS acm documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for consistency. Added guidance about wildcard certificate usage with CloudFormation templates to avoid certificate quota exhaustion.
Security assessment
The changes are stylistic updates to terminology and best practice recommendations for certificate management efficiency. While discussing certificate quotas and validation methods, there is no indication of addressing a specific security vulnerability or weakness.
Diff
diff --git a/acm/latest/userguide/acm-bestpractices.md b/acm/latest/userguide/acm-bestpractices.md index 3b01df23f..24f7d330a 100644 --- a//acm/latest/userguide/acm-bestpractices.md +++ b//acm/latest/userguide/acm-bestpractices.md @@ -65 +65 @@ JSON -With AWS CloudFormation you can create a template that describes the AWS resources that you want to use. AWS CloudFormation then provisions and configures those resources for you. AWS CloudFormation can provision resources that are supported by ACM such as Elastic Load Balancing, Amazon CloudFront, and Amazon API Gateway. For more information, see [Services integrated with ACM](./acm-services.html). +With AWS CloudFormation you can create a template that describes the AWS resources that you want to use. CloudFormation then provisions and configures those resources for you. CloudFormation can provision resources that are supported by ACM such as Elastic Load Balancing, Amazon CloudFront, and Amazon API Gateway. For more information, see [Services integrated with ACM](./acm-services.html). @@ -67 +67 @@ With AWS CloudFormation you can create a template that describes the AWS resourc -If you use AWS CloudFormation to quickly create and delete multiple test environments, we recommend that you do not create a separate ACM certificate for each environment. Doing so will quickly exhaust your certificate quota. For more information, see [Quotas](./acm-limits.html). Instead, create a wildcard certificate that covers all of the domain names that you are using for testing. For example, if you repeatedly create ACM certificates for domain names that vary by only a version number, such as `<version>``.service.example.com`, create instead a single wildcard certificate for `<*>``.service.example.com`. +If you use CloudFormation to quickly create and delete multiple test environments, we recommend that you do not create a separate ACM certificate for each environment. Doing so will quickly exhaust your certificate quota. For more information, see [Quotas](./acm-limits.html). Instead, create a wildcard certificate that covers all of the domain names that you are using for testing. For example, if you repeatedly create ACM certificates for domain names that vary by only a version number, such as `<version>``.service.example.com`, create instead a single wildcard certificate for `<*>``.service.example.com`. @@ -71 +71 @@ If you use AWS CloudFormation to quickly create and delete multiple test environ -If you're using Amazon CloudFront distributions, note that HTTP validation doesn't support wildcard certificates. When including wildcard certificates in your AWS CloudFormation templates for use with Amazon CloudFront, you must use either DNS validation or email validation. We recommend DNS validation for automated renewal capabilities. +If you're using Amazon CloudFront distributions, note that HTTP validation doesn't support wildcard certificates. When including wildcard certificates in your CloudFormation templates for use with Amazon CloudFront, you must use either DNS validation or email validation. We recommend DNS validation for automated renewal capabilities. @@ -73 +73 @@ If you're using Amazon CloudFront distributions, note that HTTP validation doesn -Include the wildcard certificate in the template that AWS CloudFormation uses to create your test environment. +Include the wildcard certificate in the template that CloudFormation uses to create your test environment.