cloud —

AWS PrivateLink Tunnel Endpoints Open a Whole CIDR Range to Another Account

The provider shares a CIDR-type resource configuration through AWS Resource Access Manager and the consumer creates a tunnel endpoint against it.

AWS PrivateLink Tunnel Endpoints Open a Whole CIDR Range to Another Account

From then on, anything inside the range is reachable, including resources that did not exist when the share was made. Bruce Pinsky and Ashish Kumar of AWS frame it as a vendor-access problem, for "a vendor or service provider whose software must reach applications and resources in a customer's network."

Until now, that meant a separate PrivateLink resource configuration per database or host, which breaks down when the resources are ephemeral, or the customer does not want to enumerate them. With a CIDR configuration, the customer defines a perimeter in address ranges, and "resources located outside the perimeter can't be reached by the vendor."

Two further properties come with the design: the consumer and provider VPCs can use overlapping CIDR blocks, and connections "can start only from the consumer VPC, not from the provider network." (Source: AWS Networking & Content Delivery blog) On the r/aws thread about the September launch, the first question was what this does that VPC peering does not, from a self-described veteran of AWS's advanced networking components.

Earlier coverage

Reported by infoq.com.

cloud

Related coverage

Elsewhere in this edition