AWS prescriptive-guidance documentation change
Summary
Replaced 'AWS VPN services' with 'Site-to-Site VPN services' in VPC encryption guidance
Security assessment
Terminology consistency update. No security implications as the guidance about using PrivateLink to avoid internet exposure remains identical.
Diff
diff --git a/prescriptive-guidance/latest/encryption-best-practices/vpc.md b/prescriptive-guidance/latest/encryption-best-practices/vpc.md index c1afc667a..daa0660d8 100644 --- a//prescriptive-guidance/latest/encryption-best-practices/vpc.md +++ b//prescriptive-guidance/latest/encryption-best-practices/vpc.md @@ -19 +19 @@ Consider the following encryption best practices for this service: - * Use VPC endpoints in AWS PrivateLink to privately connect your VPCs to supported AWS services without using an internet gateway. You can use AWS Direct Connect or AWS VPN services to establish this connection. Traffic between your VPC and the other service does not leave the AWS network. For more information, see [Access AWS services through AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-aws-services.html). + * Use VPC endpoints in AWS PrivateLink to privately connect your VPCs to supported AWS services without using an internet gateway. You can use AWS Direct Connect or Site-to-Site VPN services to establish this connection. Traffic between your VPC and the other service does not leave the AWS network. For more information, see [Access AWS services through AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-aws-services.html).