Network and Content Delivery
CoreAWS PrivateLink
Explicit private-connectivity example and endpoint boundary.
Key points
- PrivateLink exposes selected provider services through endpoint services and consumer interface endpoints without merging route domains.
Best-known use cases
- D2.1, D2.2, and D5.1: publish or consume one named private service without a peering mesh.
What candidates often confuse it with
- PrivateLink provides service-oriented private access; VPC peering provides routed VPC-to-VPC connectivity.
Key takeaway
Verify provider authorization, consumer endpoint subnets, security groups, DNS, policy, and Region.
Related services
- Amazon Application Recovery Controller
- AWS Client VPN
- Amazon CloudFront
Relevant exam tasks
- D2.1 — Task 2.1: Implement scalability and elasticity.
- 2.1.1 — Configure and manage scaling mechanisms in compute environments.
- D2.2 — Task 2.2: Implement highly available and resilient environments.
- 2.2.1 — Configure and troubleshoot Elastic Load Balancing (ELB) and Amazon Route 53 health checks.
- D5.1 — Task 5.1: Implement and optimize networking features and connectivity.
- 5.1.1 — Configure a VPC (for example, subnets, route tables, network ACLs, security groups, NAT gateways, internet gateway, egress-only internet gateway).