AWS AmazonCloudFront documentation change
Summary
Added wildcard domain documentation for distribution tenants
Security assessment
Documents support for wildcard certificates in specific scenarios. While wildcards have security considerations, this change simply clarifies existing capabilities rather than addressing a security issue.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/managed-cloudfront-certificates.md b/AmazonCloudFront/latest/DeveloperGuide/managed-cloudfront-certificates.md index 8c0f8dd9e..a5a2e6933 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/managed-cloudfront-certificates.md +++ b//AmazonCloudFront/latest/DeveloperGuide/managed-cloudfront-certificates.md @@ -5 +5 @@ -Add a domain and certificate (distribution tenant)Complete domain setupPoint domains to CloudFrontDomain considerations (distribution tenant) +Add a domain and certificate (distribution tenant)Complete domain setupPoint domains to CloudFrontDomain considerations (distribution tenant)Wildcard domains (distribution tenant) @@ -28,0 +29,2 @@ You can request the certificate when you create or update the distribution tenan + * Wildcard domains (distribution tenant) + @@ -255,0 +258,11 @@ You don't need to call the ACM API operations to create or update your certifica +## Wildcard domains (distribution tenant) + +Wildcard domains are supported for distribution tenants in the following situations: + + * When the wildcard is included in the shared certificate that's inherited from the parent multi-tenant distribution + + * When you use a valid existing custom TLS certificate for your distribution tenant + + + +