Services

Resources

Company

AWS PrivateLink

AWS PrivateLink lets a consumer reach a service in another VPC or AWS account over private IP addresses, without an internet gateway, NAT or VPC peering. SaaS vendors use it to offer customers a private API endpoint, and AWS uses it for its own services through interface VPC endpoints.

How it works

The provider puts a Network Load Balancer in front of the service and creates a VPC endpoint service, then allows specific AWS accounts to connect. Each consumer creates an interface VPC endpoint, which places network interfaces with private IPs in the consumer's own subnets. Connections can only be started from the consumer side.

For example, three customers can each reach a vendor's API at private addresses inside their own VPCs, even if all three VPCs use 10.0.0.0/16. VPC peering cannot connect overlapping ranges like that, and it would also open the networks to each other.

Why it matters in production

PrivateLink is regional and billed per endpoint per Availability Zone per hour plus per GB processed, so the bill grows with customers and zones. Enable the endpoint service in at least two zones, use private DNS so clients keep the same hostname, and plan cross-region access before a customer asks for it.

See also

On the One2N blog

References

  1. AWS PrivateLink documentation

  2. Share your services through AWS PrivateLink

Comic about AWS PrivateLink: a SaaS provider serves an API through an NLB endpoint service to three customer VPCs, all using 10.0.0.0/16; each customer app calls its own interface endpoint, such as 10.0.1.25, with no peering or VPN; traffic stays on the AWS network with no internet gateway, NAT or public IP; overlapping ranges are fine, and only customers can open connections.