- Newest
- Most votes
- Most comments
Can you explain your use-case? API Gateway itself can expose your service to the public. API Gateway supports Regional or Edge Optimized endpoints that are external facing. So why do you want to add ALB in front of API Gateway again. What are you planning to achieve with that architecture?
Can you try using the private IP from Network Interfaces attached to the API Gateway as the ALB Target. But the Private IP can change so you need to have some custom solution(may be lambda) to monitor the IP change.
you need to use HTTP integration https://docs.aws.amazon.com/apigateway/latest/developerguide/getting-started-http-integrations.html see the following guide https://aws.amazon.com/premiumsupport/knowledge-center/api-gateway-application-load-balancers/
Relevant content
- asked 2 years ago
- asked a year ago
- asked 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
We plan to use ALB to expose our portal, API gateway works for backend. API gateway cannot be access from public for china regions aws account default configuration(some china regions policy), so we want to use ALB to handle all request from public, and then forward to API Gateway.