AWS acm: Drop email validation from wildcard certificate guidance
Summary
Two statements recommending DNS or email validation for wildcard certificates now recommend DNS validation only, consistent with the deprecation of email validation.
Security assessment
Removes the now-deprecated email validation option from wildcard certificate guidance, leaving DNS validation. Minor accuracy/maintenance wording change with no direct security control impact.
Evidence
+Indicates that the ACM CA that you specified in the **value** field is authorized to issue a wildcard certificate for your domain or subdomain. A wildcard certificate applies to the domain or subdomain and all of its subdomains. Note that if you plan to use HTTP validation, this setting won't apply because HTTP validation doesn't support wildcard certificates. Use DNS validation instead for wildcard certificates.
Diff
diff --git a/acm/latest/userguide/setup.md b/acm/latest/userguide/setup.md index 86b7aef..c7d5f36 100644 --- a//acm/latest/userguide/setup.md +++ b//acm/latest/userguide/setup.md @@ -60 +60 @@ Indicates that the ACM CA that you specify in the **value** field is authorized -Indicates that the ACM CA that you specified in the **value** field is authorized to issue a wildcard certificate for your domain or subdomain. A wildcard certificate applies to the domain or subdomain and all of its subdomains. Note that if you plan to use HTTP validation, this setting won't apply because HTTP validation doesn't support wildcard certificates. Use DNS or email validation instead for wildcard certificates. +Indicates that the ACM CA that you specified in the **value** field is authorized to issue a wildcard certificate for your domain or subdomain. A wildcard certificate applies to the domain or subdomain and all of its subdomains. Note that if you plan to use HTTP validation, this setting won't apply because HTTP validation doesn't support wildcard certificates. Use DNS validation instead for wildcard certificates. @@ -98 +98 @@ In the following examples, your domain name comes first followed by the record t -If you plan to use HTTP validation with CloudFront, you don't need to configure **issuewild** records because HTTP validation doesn't support wildcard certificates. For wildcard certificates, use DNS or email validation instead. +If you plan to use HTTP validation with CloudFront, you don't need to configure **issuewild** records because HTTP validation doesn't support wildcard certificates. For wildcard certificates, use DNS validation instead.