Networking and Content Delivery
CoreAWS PrivateLink
Private service connectivity between consumers and supported services through interface VPC endpoints without broad network routing.
Key points
- PrivateLink is service-specific and non-transitive, limiting the consumer/provider network relationship.
- It can support overlapping consumer/provider address spaces because consumers connect to endpoint IPs rather than provider routes.
- Endpoint placement, private DNS, policies, security groups, and service authorization all affect the path.
Best-known use cases
- Expose a SaaS or shared service privately across VPCs/accounts.
- Reach supported AWS services privately from a VPC.
What candidates often confuse it with
- PrivateLink exposes one service; VPC peering or Transit Gateway connects routed networks.
- PrivateLink endpoints provide private access; NAT provides general outbound access.
Key takeaway
Choose PrivateLink when private service access is required without full network connectivity.
Related services
- Amazon VPC
- AWS Transit Gateway
- Elastic Load Balancing (ELB)
Relevant exam tasks
- D1.2
- D3.4
- D4.4