AWS apigateway documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in network connection documentation
Security assessment
The change appears to be a minor branding/style update rather than addressing security functionality. No security implications or vulnerability fixes are mentioned in the context of this edit.
Diff
diff --git a/apigateway/latest/developerguide/security-traffic-privacy.md b/apigateway/latest/developerguide/security-traffic-privacy.md index 6ba26f714..cbdf2cbc1 100644 --- a//apigateway/latest/developerguide/security-traffic-privacy.md +++ b//apigateway/latest/developerguide/security-traffic-privacy.md @@ -7 +7 @@ -Using Amazon API Gateway, you can create private REST APIs that can be accessed only from your Amazon Virtual Private Cloud (VPC). The VPC uses an [interface VPC endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html), which is an endpoint network interface that you create in your VPC. Using [ resource policies](./apigateway-private-api-create.html#apigateway-private-api-set-up-resource-policy), you can allow or deny access to your API from selected VPCs and VPC endpoints, including across AWS accounts. Each endpoint can be used to access multiple private APIs. You can also use AWS Direct Connect to establish a connection from an on-premises network to Amazon VPC and access your private API over that connection. In all cases, traffic to your private API uses secure connections and does not leave the Amazon network; it is isolated from the public internet. To learn more, see [Private REST APIs in API Gateway](./apigateway-private-apis.html). +Using Amazon API Gateway, you can create private REST APIs that can be accessed only from your Amazon Virtual Private Cloud (VPC). The VPC uses an [interface VPC endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html), which is an endpoint network interface that you create in your VPC. Using [ resource policies](./apigateway-private-api-create.html#apigateway-private-api-set-up-resource-policy), you can allow or deny access to your API from selected VPCs and VPC endpoints, including across AWS accounts. Each endpoint can be used to access multiple private APIs. You can also use Direct Connect to establish a connection from an on-premises network to Amazon VPC and access your private API over that connection. In all cases, traffic to your private API uses secure connections and does not leave the Amazon network; it is isolated from the public internet. To learn more, see [Private REST APIs in API Gateway](./apigateway-private-apis.html).