Question

A financial services company runs a payment processing service behind a Network Load Balancer in an eu-west-1 VPC and exposes it via an AWS PrivateLink endpoint service. A newly acquired subsidiary operates all of its workloads in us-east-1 and must consume this service privately, without traversing the public internet and without requiring the two organizations to coordinate on overlapping RFC 1918 address spaces. The networking team wants the simplest design that keeps traffic on the AWS backbone. Which approach should they implement?

Accepted Answer

Enable cross-Region access on the PrivateLink endpoint service, then create an interface VPC endpoint in the us-east-1 consumer VPC that points to the eu-west-1 endpoint service.

Answer

Establish an inter-Region VPC peering connection between the us-east-1 and eu-west-1 VPCs and add routes to the NLB's private IP addresses in each route table.

Answer

Attach both VPCs to a Transit Gateway in each Region, peer the Transit Gateways across Regions, and route consumer traffic directly to the NLB subnets in eu-west-1.

Answer

Create a Direct Connect gateway associating the two Regions and advertise the NLB subnet prefixes so the subsidiary can reach the service privately.