AWS whitepapers documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint connectivity documentation
Security assessment
Minor terminology adjustment without altering technical meaning. No evidence of addressing a security vulnerability or introducing security features.
Diff
diff --git a/whitepapers/latest/building-a-data-perimeter-on-aws/perimeter-overview.md b/whitepapers/latest/building-a-data-perimeter-on-aws/perimeter-overview.md index 57fcc62e5..b0b8c8d69 100644 --- a//whitepapers/latest/building-a-data-perimeter-on-aws/perimeter-overview.md +++ b//whitepapers/latest/building-a-data-perimeter-on-aws/perimeter-overview.md @@ -81 +81 @@ These policies are a special type of resource-based policy that you attach to an -For on-premises networks, you can also route AWS traffic through VPC endpoints if they are connected to AWS with AWS Direct Connect or a VPN. For services that have [AWS PrivateLink](https://aws.amazon.com/privatelink/) interface endpoints, you can route traffic to those endpoints directly from an on-premises network. For a list of services that support VPC endpoints and VPC endpoint policies, refer to [AWS services that integrate with AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/integrated-services-vpce-list.html). +For on-premises networks, you can also route AWS traffic through VPC endpoints if they are connected to AWS with Direct Connect or a VPN. For services that have [AWS PrivateLink](https://aws.amazon.com/privatelink/) interface endpoints, you can route traffic to those endpoints directly from an on-premises network. For a list of services that support VPC endpoints and VPC endpoint policies, refer to [AWS services that integrate with AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/integrated-services-vpce-list.html).