AWS apigateway documentation change
Summary
Marked Network Load Balancer setup for API Gateway private integrations as legacy, added note recommending VPC links V2 instead of V1, and updated section headers to reflect legacy status.
Security assessment
The changes deprecate VPC links V1 but provide no evidence of security vulnerabilities. Updates are versioning recommendations without security implications.
Diff
diff --git a/apigateway/latest/developerguide/set-up-nlb-for-vpclink-using-console.md b/apigateway/latest/developerguide/set-up-nlb-for-vpclink-using-console.md index 97f380988..6e95053eb 100644 --- a//apigateway/latest/developerguide/set-up-nlb-for-vpclink-using-console.md +++ b//apigateway/latest/developerguide/set-up-nlb-for-vpclink-using-console.md @@ -5 +5 @@ -# Set up a Network Load Balancer for API Gateway private integrations +# Set up a Network Load Balancer for API Gateway private integrations (legacy) @@ -7 +7 @@ -The following procedure outlines the steps to set up a Network Load Balancer (NLB) for API Gateway private integrations using the Amazon EC2 console and provides references for detailed instructions for each step. +###### Note @@ -9 +9 @@ The following procedure outlines the steps to set up a Network Load Balancer (NL -For each VPC you have resources in, you only need to configure one NLB and one VPCLink. The NLB supports multiple [listeners](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-listeners.html) and [target groups](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html) per NLB. You can configure each service as a specific listener on the NLB and use a single VPCLink to connect to the NLB. When creating the private integration in API Gateway you then define each service using the specific port that is assigned for each service. For more information, see [Tutorial: Create a REST API with a private integration](./getting-started-with-private-integration.html). +The following implementation of private integrations uses VPC links V1. VPC links V1 are legacy resources. We recommend that you use [VPC links V2 for REST APIs](./apigateway-vpc-links-v2.html). @@ -11 +11 @@ For each VPC you have resources in, you only need to configure one NLB and one V -###### Note +The following procedure outlines the steps to set up a Network Load Balancer (NLB) for API Gateway private integrations using the Amazon EC2 console and provides references for detailed instructions for each step. @@ -13 +13 @@ For each VPC you have resources in, you only need to configure one NLB and one V -The Network Load Balancer and API must be owned by the same AWS account. +For each VPC you have resources in, you only need to configure one NLB and one VPCLink. The NLB supports multiple [listeners](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-listeners.html) and [target groups](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html) per NLB. You can configure each service as a specific listener on the NLB and use a single VPCLink to connect to the NLB. When creating the private integration in API Gateway you then define each service using the specific port that is assigned for each service. For more information, see [Tutorial: Create a REST API with a private integration](./getting-started-with-private-integration.html). The Network Load Balancer and API must be owned by the same AWS account. @@ -49 +49 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Private integration +Private integration using VPC links V1 (legacy) @@ -51 +51 @@ Private integration -Grant permissions for API Gateway to create a VPC link +Grant permissions for API Gateway to create a VPC link (legacy)