AWS apigateway documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' and CloudFormation references
Security assessment
Branding updates without altering private API security mechanisms or configurations
Diff
diff --git a/apigateway/latest/developerguide/apigateway-private-api-test-invoke-url.md b/apigateway/latest/developerguide/apigateway-private-api-test-invoke-url.md index 66696350c..89e070385 100644 --- a//apigateway/latest/developerguide/apigateway-private-api-test-invoke-url.md +++ b//apigateway/latest/developerguide/apigateway-private-api-test-invoke-url.md @@ -104 +104 @@ If you enable private DNS for your VPC endpoint, you won't be able to access the -### Invoke a private API using AWS Direct Connect +### Invoke a private API using Direct Connect @@ -106 +106 @@ If you enable private DNS for your VPC endpoint, you won't be able to access the -You can use AWS Direct Connect to establish a dedicated private connection from an on-premises network to Amazon VPC and access your private API endpoint over that connection by using public DNS names. +You can use Direct Connect to establish a dedicated private connection from an on-premises network to Amazon VPC and access your private API endpoint over that connection by using public DNS names. @@ -135 +135 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Create a custom domain name for private APIs using AWS CloudFormation +Create a custom domain name for private APIs using CloudFormation