AWS PrivateLink Tunnel Endpoints opens up an entire CIDR range to another account

- Reading
- 5 min
- Code
- 1
Launched in September, PrivateLink's tunnel endpoints eliminate the need to register each resource individually to grant access between AWS accounts; a technical walkthrough published by AWS details how it works and the limits already tested by the community.
In November, AWS published a technical walkthrough on tunnel endpoints, a type of VPC endpoint launched in September 2026 that changes how an application in one account accesses resources in another. Instead of registering a separate PrivateLink for each database or host, the provider shares an entire address range (a CIDR) via AWS Resource Access Manager, and the consumer creates a single tunnel endpoint against that range. From then on, anything inside the range becomes accessible, including resources that didn't exist yet when the share was created.
The original post, written by Bruce Pinsky and Ashish Kumar of AWS, describes the problem as typical of a software vendor that needs to reach a customer's network:
A vendor or service provider whose software must reach applications and resources in a customer's network.
Bruce Pinsky and Ashish Kumar, AWS Networking & Content Delivery blog
Before tunnel endpoints, this model required one PrivateLink resource configuration per database or host, something unworkable when resources are ephemeral or the customer doesn't want (or can't) list each one manually.
Why not use VPC peering
The first question in the r/aws thread about the launch, in September, came from a user who described themselves as a veteran of AWS advanced networking components: what's the practical difference from VPC peering? The replies in the thread itself map out the use cases. Peering exposes the entire VPC in both directions; the tunnel endpoint shares only a subset of the address space, and in a single direction.
A commenter who works in banking summed up why this matters in a regulated environment:
peering with unregulated partners is a massive no-no, the auditors will rip you to shreds for it.
banking professional, comment on r/aws
Another point raised in the same thread: clusters that do client-side load balancing, such as self-managed Kafka or Aerospike, previously needed port-based routing on a Network Load Balancer, with a separate port-mapping scope for connections via interface endpoint. The dividing line is in relation to VPC Lattice: Lattice services operate at layer 7, while tunnel endpoints work at layer 4, without requiring a resource configuration per target.
How traffic reaches the other side
The less obvious part is on the consumer side. Application traffic needs to reach the tunnel endpoint encapsulated in GENEVE, the protocol defined in RFC 8926, via UDP on port 6081, and within the same availability zone. The endpoint strips the header, checks whether the internal destination falls within the shared range, rewrites the source to a resource gateway address, and forwards an ordinary packet into the provider's VPC.
On Linux, this encapsulation can run directly in the kernel. AWS's walkthrough creates the interface with:
ip link add geneve0 type geneve id 0 remote <endpoint-ip> dstport 6081inside the instance's own network namespace, with a default route passing through it. This routes only the provider's ranges into the tunnel and leaves the rest of the instance's traffic untouched. On the other side, resources see the resource gateway as the client, not the real source, which leads AWS to recommend security groups that reference the gateway's security group or subnet, rather than a single address.
Restrictions that change the solution's design
The documentation lists a series of limits that directly affect the architecture:
- Internal traffic must be TCP; UDP is only allowed for DNS, so ICMP and ping don't work.
- IP fragments are dropped.
- Private DNS names are not supported on tunnel endpoints.
- The endpoint's subnets need to be in availability zones that overlap with the resource gateway's, or the association shows up as unreachable.
- A resource gateway's DNS configuration cannot be changed after it's created.
Access logs identify the consumer's endpoint, but have no field for the internal source address. In practice, a provider can attribute traffic to a vendor, but not to a specific workload behind that vendor's endpoint. AWS also warns that sharing 0.0.0.0/0 grants access to everything the provider's VPC can route to, including networks behind VPC peering, Direct Connect, or a Site-to-Site VPN, and recommends sharing the narrowest ranges possible.
What the community has already tested
Ryo Suzuki, from the Japanese consultancy Classmethod, put AWS's two warning scenarios to the test in practice. In the first, he connected two VPCs that use the same 10.0.0.0/16 block and got HTTP traffic flowing, but only by running a GENEVE relay as root on the client, routing a /32 per destination, or putting a HAProxy or NAT instance in front, solutions that add a hop or a single point of failure. His conclusion:
route management according to the number of destinations is required.
Ryo Suzuki, Classmethod
In the second test, Suzuki shared 0.0.0.0/0 from a VPC with a NAT gateway and managed to reach the internet from a VPC with no NAT gateway of its own, confirming AWS's warning from the opposite angle. His verdict: viable as a temporary path, but:
difficult to use in a permanent production setup.
Ryo Suzuki, Classmethod
Pricing, regions, and Terraform
The billing model follows PrivateLink's pricing table: an hourly fee per tunnel endpoint, plus a fee per GB of data processed. On the provider side, billing is per GB through the resource gateway, under VPC Lattice's pricing table. The feature is available in 28 regions.
Terraform support came from the community, not directly from AWS: a contribution request opened two days after the September launch was implemented by another contributor and landed in version 6.71.0 of the AWS provider, with a Tunnel endpoint type on the aws_vpc_endpoint resource and a cidr_resource block in the Lattice resource configuration.
What changes for those designing the network
For architects dealing with overlapping VPCs, the combination of two design points is what sets this endpoint apart from traditional peering: consumer and provider VPCs can use identical CIDR blocks, and connections can only originate from the consumer VPC, never from the provider's network. This fits well in vendor-customer scenarios, where the vendor should never initiate a connection into the customer's network.
But Ryo Suzuki's tests make it clear that overlapping CIDRs don't solve routing by magic: it's still necessary to deal with NAT, relay, or per-host routing when both sides use the same address block. Anyone evaluating the feature to replace resource-by-resource PrivateLink in ephemeral clusters (Kafka, Aerospike, self-managed databases) gains operational simplicity, but inherits the restrictions of TCP-only traffic, no private DNS, and logs without an internal source IP, which need to factor into the security and audit assessment before any migration.
Translated from the Brazilian Portuguese original · Read the original
Vercel launches UI SDK for AI agents to compose interfaces with reusable building blocks
Open source library in beta treats keyboard navigation, focus, selection, and drag and drop as reusable behaviors, with a dedicated API for agents to operate components without relying on screenshots.






