AWS acm: Update HTTP validation comparison wording in ACM concepts
Summary
Rewords the HTTP validation concept to compare against DNS-validated certificates instead of email- or DNS-validated certificates.
Security assessment
Terminology cleanup removing the email-validation reference; no security behavior or guidance change beyond wording.
Evidence
+Unlike DNS-validated certificates, you can't issue HTTP-validated certificates directly from ACM. Instead, these certificates are automatically issued and managed as part of the CloudFront provisioning process. Customers can use ACM to view, monitor, and manage these certificates, but the initial issuance is handled by the integration between ACM and CloudFront.
Diff
diff --git a/acm/latest/userguide/acm-concepts.md b/acm/latest/userguide/acm-concepts.md index 1263b83..77c0391 100644 --- a//acm/latest/userguide/acm-concepts.md +++ b//acm/latest/userguide/acm-concepts.md @@ -266 +266 @@ In the context of ACM, HTTP can be used for domain validation when issuing SSL/T -Unlike email or DNS-validated certificates, ACM customers can't issue HTTP-validated certificates directly from ACM. Instead, these certificates are automatically issued and managed as part of the CloudFront provisioning process. Customers can use ACM to view, monitor, and manage these certificates, but the initial issuance is handled by the integration between ACM and CloudFront. +Unlike DNS-validated certificates, you can't issue HTTP-validated certificates directly from ACM. Instead, these certificates are automatically issued and managed as part of the CloudFront provisioning process. Customers can use ACM to view, monitor, and manage these certificates, but the initial issuance is handled by the integration between ACM and CloudFront.