Question

A company is deploying a new microservices platform in IPv6-only subnets within a VPC to conserve IPv4 address space. The services must be able to reach an external partner API that is only reachable via an IPv4 public endpoint (no AAAA record exists for it). The networking team needs a solution that allows the IPv6-only workloads to initiate outbound connections to this IPv4-only destination without assigning IPv4 addresses to the workload instances. Which combination of features should the team enable to achieve this?

Accepted Answer

Enable DNS64 on the subnet's associated Route 53 Resolver and route IPv6 traffic destined for the well-known NAT64 prefix (64:ff9b::/96) to a NAT gateway

Answer

Attach an egress-only internet gateway to the VPC and add a default IPv6 route pointing to it

Answer

Enable a Route 53 Resolver outbound endpoint with a forwarding rule for the partner domain and route through a Direct Connect gateway

Answer

Assign IPv6 addresses from a BYOIP pool and configure PrivateLink to the partner's endpoint service