AWS acm: DNS validation: switch from email via UpdateCertificateOptions
Summary
Updates guidance to switch an existing certificate from email to DNS validation using UpdateCertificateOptions, and raises the CNAME chaining limit from five to eight.
Security assessment
The change documents a supported API path to migrate to DNS validation (a stronger domain-ownership validation method) and adjusts a CNAME chaining limit; it is security-adjacent guidance, not a specific vulnerability fix.
Evidence
+To switch an existing certificate from email validation to DNS validation, use the [`UpdateCertificateOptions`](https://docs.aws.amazon.com/acm/latest/APIReference/API_UpdateCertificateOptions.html) API.
Diff
diff --git a/acm/latest/userguide/dns-validation.md b/acm/latest/userguide/dns-validation.md index 5e5a94f..cfa1ff9 100644 --- a//acm/latest/userguide/dns-validation.md +++ b//acm/latest/userguide/dns-validation.md @@ -15 +15 @@ The Domain Name System (DNS) is a directory service for resources that are conne -After you create a certificate with email validation, you cannot switch to validating it with DNS. To use DNS validation, delete the certificate and then create a new one that uses DNS validation. +To switch an existing certificate from email validation to DNS validation, use the [`UpdateCertificateOptions`](https://docs.aws.amazon.com/acm/latest/APIReference/API_UpdateCertificateOptions.html) API. @@ -29 +29 @@ You can stop automatic renewal either by removing the certificate from the AWS s -CNAME resolution will fail if more than five CNAMEs are chained together in your DNS configuration. If you require a longer chaining, we recommend using [email validation](./email-validation.html). +CNAME resolution will fail if more than eight CNAMEs are chained together in your DNS configuration.