← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

AWS PrivateLink Tunnel Endpoints Allow CIDR Range Sharing Between Accounts

🔄 Updated 3d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Tunnel endpoints share an entire CIDR range, not individual resources.
  • Uses AWS Resource Access Manager for CIDR-type resource configuration.
  • Consumer VPCs initiate connections; provider VPCs cannot.
  • Supports overlapping CIDR blocks between consumer and provider VPCs.
  • Traffic must be encapsulated in GENEVE protocol on the consumer side.

New VPC Endpoint Type for CIDR Sharing

AWS introduced tunnel endpoints, a new VPC endpoint type that allows an application in one Virtual Private Cloud (VPC) to reach every address within a specified CIDR range shared from another AWS account. This capability was launched in September and a technical walkthrough has been published by AWS.

Previously, sharing access to multiple resources often required individual PrivateLink resource configurations for each database or host. This approach became impractical for ephemeral resources or when customers did not want to enumerate every resource.

Addressing Vendor Access Challenges

AWS frames this feature as a solution for vendors or service providers whose software needs to access applications and resources within a customer's network. With a CIDR configuration, customers can define a perimeter using address ranges, ensuring that only resources within that perimeter are reachable by the vendor.

The design includes two key properties: consumer and provider VPCs can use overlapping CIDR blocks, and connections can only originate from the consumer VPC, not from the provider network.

Distinction from VPC Peering and Other Services

Tunnel endpoints differ from VPC peering, which exposes an entire VPC in both directions. Tunnel endpoints share a subset of the address space in one direction only, offering more granular control. This is particularly relevant for regulated environments where sharing an entire VPC with external partners is not permissible.

The feature also provides an alternative for client-side load balancing clusters (e.g., self-managed Kafka or Aerospike) that previously required port-based routing on a Network Load Balancer and separate port mapping. Unlike VPC Lattice, which operates at Layer 7, tunnel endpoints function at Layer 4 without requiring a resource configuration per target.

Technical Implementation Details

On the consumer side, application traffic must arrive at the tunnel endpoint encapsulated in GENEVE (Generic Network Virtualization Encapsulation) protocol, as defined in RFC 8926. This traffic uses UDP port 6081 and must originate from within the same Availability Zone as the endpoint. The endpoint then strips the GENEVE header and performs validation.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

AWS launched a new VPC endpoint type called tunnel endpoints, enabling applications in one VPC to access an entire CIDR range shared from another account. This feature addresses challenges in vendor access by allowing a single configuration to cover multiple resources within a defined address space, rather than requiring individual resource configurations. It provides a more controlled and secure method for sharing network access compared to VPC peering, particularly for ephemeral resources or when strict access perimeters are necessary.