AWS apigateway documentation change
Summary
Marked VPC links V1 as legacy and recommended using VPC links V2. Updated section headers to include '(legacy)'.
Security assessment
The change deprecates V1 without citing security flaws. No vulnerability evidence exists. Impact: Encourages migration but doesn't address specific security risks.
Diff
diff --git a/apigateway/latest/developerguide/grant-permissions-to-create-vpclink.md b/apigateway/latest/developerguide/grant-permissions-to-create-vpclink.md index a6e09d1b9..a9da1ef65 100644 --- a//apigateway/latest/developerguide/grant-permissions-to-create-vpclink.md +++ b//apigateway/latest/developerguide/grant-permissions-to-create-vpclink.md @@ -5 +5,5 @@ -# Grant permissions for API Gateway to create a VPC link +# Grant permissions for API Gateway to create a VPC link (legacy) + +###### Note + +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). @@ -71 +75 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Set up a Network Load Balancer for private integrations +Set up a Network Load Balancer for private integrations (legacy) @@ -73 +77 @@ Set up a Network Load Balancer for private integrations -Set up an API with private integrations using AWS CLI +Set up an API with private integrations using AWS CLI (legacy)