AWS acm documentation change
Summary
Changed 'customer-managed infrastructure' to 'your managed infrastructure' in ACME certificate usage guidance
Security assessment
Minor terminology update without security implications. Maintains existing security guidance about private key management.
Diff
diff --git a/acm/latest/userguide/acm-acme.md b/acm/latest/userguide/acm-acme.md index 112d44294..c8518ea68 100644 --- a//acm/latest/userguide/acm-acme.md +++ b//acm/latest/userguide/acm-acme.md @@ -96 +96 @@ The following operational behaviors and constraints apply to ACME-issued certifi - * **AWS integrated services:** ACME-issued certificates cannot be bound to [Managed automation with integrated services](./acm-services.html) such as Elastic Load Balancing, CloudFront, or API Gateway. Use the certificate on the customer-managed infrastructure where the ACME client holds the private key. + * **AWS integrated services:** ACME-issued certificates cannot be bound to [Managed automation with integrated services](./acm-services.html) such as Elastic Load Balancing, CloudFront, or API Gateway. Use the certificate on your managed infrastructure where the ACME client holds the private key.