Network and Content Delivery
CoreVPC peering
Explicit private-connectivity example and non-transitive routing boundary.
Key points
- VPC peering supplies direct routing between non-overlapping VPCs and does not provide transitive connectivity.
Best-known use cases
- D2.1, D2.2, and D5.1: connect or troubleshoot two named VPCs with routes, DNS, filters, and return paths on both sides.
What candidates often confuse it with
- Peering joins two VPC route domains directly; Transit Gateway provides hub routing and PrivateLink exposes one service.
Key takeaway
A peering connection is incomplete until both VPCs have compatible CIDRs, routes, DNS choices, filters, and return traffic.
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).