For cloud architects and developers building microservices on AWS, exposing internal services securely has just gotten significantly easier.
Amazon Web Services has announced a major improvement to networking patterns: the ability to create direct private integrations between Amazon API Gateway and private Application Load Balancers (ALBs).
The Old Way vs. The New Way
Previously, if you wanted to expose a service running in a private subnet behind an ALB to an API Gateway, the architecture was unnecessarily complex. You often had to place a Network Load Balancer (NLB) in front of the ALB just to bridge the connection via a VPC Link. This setup worked, but it introduced an extra hop, increased latency, and added another component to manage and pay for.
That requirement is now gone.
With this update, you can utilize VPC Link v2 to connect API Gateway directly to your internal Application Load Balancers.
Why This Matters for Your Architecture
This update simplifies how enterprises build scalable, private REST APIs. By removing the intermediate NLB, you gain several immediate benefits:
Simplified Infrastructure: Less operational overhead by removing unnecessary networking components.
Reduced Latency: Traffic flows directly from the API Gateway to the ALB, eliminating an extra network hop.
Enhanced Layer 7 Routing: You can now leverage the advanced routing capabilities of ALBs (like path-based or host-based routing) directly from your API Gateway private integration.
Improved Scalability: A single VPC Link v2 can now connect to multiple ALBs within your VPC, allowing for cleaner fan-out architectures.
Read the Full Implementation Guide
If you are currently using the NLB workaround, or if you are planning a new microservices deployment, this is the new recommended best practice.
For a complete, step-by-step walkthrough on configuring this new integration pattern, we highly recommend reading the official release on the AWS Compute Blog.