AWS amplify documentation change
Summary
Updated reference from 'ACM PCA' to 'AWS Private Certificate Authority'
Security assessment
Terminology correction with no security implications.
Diff
diff --git a/amplify/latest/userguide/encryption-in-transit.md b/amplify/latest/userguide/encryption-in-transit.md index b8fb20884..70f77076f 100644 --- a//amplify/latest/userguide/encryption-in-transit.md +++ b//amplify/latest/userguide/encryption-in-transit.md @@ -7 +7 @@ -Encryption in transit refers to protecting your data from being intercepted while it moves between communication endpoints. Amplify Hosting provides encryption for data in-transit by default. All communication between customers and Amplify and between Amplify and its downstream dependencies is protected using TLS connections that are signed using the Signature Version 4 signing process. All Amplify Hosting endpoints use SHA-256 certificates that are managed by AWS Certificate Manager Private Certificate Authority. For more information, see [Signature Version 4 signing process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) and [What is ACM PCA](https://docs.aws.amazon.com/acm-pca/latest/userguide/PcaWelcome.html). +Encryption in transit refers to protecting your data from being intercepted while it moves between communication endpoints. Amplify Hosting provides encryption for data in-transit by default. All communication between customers and Amplify and between Amplify and its downstream dependencies is protected using TLS connections that are signed using the Signature Version 4 signing process. All Amplify Hosting endpoints use SHA-256 certificates that are managed by AWS Private Certificate Authority. For more information, see [Signature Version 4 signing process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) and [What is AWS Private Certificate Authority](https://docs.aws.amazon.com/acm-pca/latest/userguide/PcaWelcome.html).