Skip to content

AWS gateway API controller usage in private subnets

0

I followed official AWS gateway API controller docs, to connect workloads using VPC lattice svc network (followed exactly same). It was working as expected in public subnet. But when my entire workload is in private subnet, the connection is not established between the workloads. My question is should I need to create Resource configurations and Resource gateways for establishing communication between workloads (when the entire cluster is created in private subnet) ?

2 Answers
1
Accepted Answer

Based on the available information about Amazon VPC Lattice and the AWS Gateway API Controller, resource configurations and resource gateways are components of VPC Lattice that can be created and managed. However, the specific requirement for using resource gateways when workloads are in private subnets is not explicitly detailed in the standard documentation.

When using the AWS Gateway API Controller with Amazon EKS to leverage VPC Lattice for cross-cluster connectivity, the service is designed to work with standard Kubernetes semantics. VPC Lattice is built directly into the AWS networking infrastructure and is intended to connect services across multiple accounts and VPCs.

For workloads in private subnets, the typical AWS pattern involves ensuring proper routing and security group configurations. When instances in private subnets need to communicate with services, they generally require appropriate route table entries and security group rules that allow the necessary traffic.

While resource gateways are a feature of VPC Lattice that can be created for specific subnets, the documentation doesn't explicitly state they are mandatory for private subnet communication. However, given that your setup works in public subnets but not in private subnets, the issue is likely related to networking configuration differences between these subnet types, such as route tables, security groups, or network ACLs that may need adjustment to allow VPC Lattice traffic in private subnets.

I recommend reviewing your security group rules, network ACLs, and route table configurations for the private subnets to ensure they permit the necessary traffic for VPC Lattice communication.
Sources
VPC Lattice examples using AWS CLI - AWS SDK Code Examples
Enable secure cross-cluster connectivity with Amazon VPC Lattice - Amazon EKS
Gateway endpoints - Amazon Virtual Private Cloud

answered 9 months ago

AWS
EXPERT

reviewed 9 months ago

  • Tnx, I added a security group rule & I was able to establish connection between workloads

0

Make sure that you have VPC endpoints in place for NAT Gateway for calls to get to AWS public service endpoints from the private subnets.

AWS
EXPERT

answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.