'AWS ApiGateway VPC Link vs HTTP Proxy integration
Well, I'm creating a AWS ApiGateway and I can't understand when I should use integration type HTTP_PROXY or VPC_LINK, both ask me URL to proxy.
I searched about it but can't found any concrect and simple example, when use one or other ?
amazon-web-servicesSolution 1:[1]
API Gateway REST API allows proxy integrations to other endpoints via two methods.
HTTP_PROXY is for Public API endpoints only.
VPC_LINK allows us to integrate API Gateway with Private Endpoints exposed via NLB (not ALB)
API Gateway HTTP API also supports both public and private integrations
- HTTP URI: For public endpoints.
- Private Resource: For NLB, ALB or CloudMap
Solution 2:[2]
I'm setting up an HTTP AWS API Gateway with Lambda integrations.
But I'm running into the issue Lambda integration requires integration_type = AWX_PROXY
But it’s incompatible with connection_type = "VPC_LINK" which requires integration_type = "HTTP_PROXY".
I can change to connection_type = "INTERNET" to make these compatible. But is this the only way?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | |
| Solution 2 | user2826721 |