Soru

Zorluk: OrtaNetworking and Connectivity Design

A company is designing a new cloud infrastructure in the us-east-1 Region. The architecture features an application VPC (vpc-prod-app, CIDR 10.10.0.0/1610.10.0.0/16) containing instances distributed across three Availability Zones (us-east-1a, us-east-1b, and us-east-1c) in private subnets. The instances require outbound-only internet access to retrieve security updates. The design must be highly available and resilient to Availability Zone failures, while minimizing data transfer charges. Additionally, the instances must resolve private domain names in the corp.internal Route 53 private hosted zone, which is hosted in a separate centralized AWS Services account. Which of the following designs should a solutions architect recommend to meet these requirements?

  1. Deploy a NAT Gateway in a public subnet in each of the three Availability Zones. Configure the route table of each private subnet to route outbound internet traffic (0.0.0.0/00.0.0.0/0) to the NAT Gateway in the same Availability Zone. Create a VPC association authorization from the centralized AWS Services account, and associate the corp.internal private hosted zone with vpc-prod-app.Cevap
  2. B
    Deploy a single NAT Gateway in a public subnet in us-east-1a. Configure the route tables of all private subnets to route outbound internet traffic (0.0.0.0/00.0.0.0/0) to this single NAT Gateway. Create a VPC association authorization from the centralized AWS Services account, and associate the corp.internal private hosted zone with vpc-prod-app.
  3. C
    Deploy a NAT Gateway in a public subnet in each of the three Availability Zones. Configure the route table of each private subnet to route outbound internet traffic (0.0.0.0/00.0.0.0/0) to the NAT Gateway in the same Availability Zone. In the centralized AWS Services account, deploy Route 53 Resolver outbound endpoints, and configure a forwarding rule for corp.internal pointing to the AWS-provided DNS IP address (10.10.0.210.10.0.2) of vpc-prod-app without associating the private hosted zone.
  4. D
    Deploy a single NAT Gateway in a centralized transit VPC. Connect vpc-prod-app to the transit VPC using an AWS Transit Gateway, and route all outbound internet traffic (0.0.0.0/00.0.0.0/0) through the Transit Gateway. Rely on the default AWS-provided DNS (10.10.0.210.10.0.2) in vpc-prod-app to resolve corp.internal without performing any cross-account associations.

Cevap

Deploy a NAT Gateway in a public subnet in each of the three Availability Zones, configure the private subnets to route outbound traffic to their local NAT Gateway, and create a cross-account VPC association for the Route 53 private hosted zone.
The correct design deploys a NAT Gateway in each Availability Zone to ensure high availability and prevent cross-AZ data transfer charges for egress traffic. For DNS resolution, a cross-account Route 53 Private Hosted Zone association is established by authorizing the association from the owner account and accepting/associating it from the VPC owner account.

Adım Adım Çözüm

1
Design the outbound internet routing for high availability and low cost.
Deploying a NAT Gateway in each Availability Zone avoids cross-AZ data transfer fees and ensures that an outage in one AZ does not affect internet connectivity in the other AZs.
Outbound traffic must not cross Availability Zones unnecessarily due to data transfer fees, and high resiliency is a key requirement.
2
Configure private DNS resolution across separate AWS accounts.
Create a VPC association authorization in the AWS Services account where the private hosted zone is defined, and then associate the zone with the application VPC using the AWS CLI, SDK, or Console.
Route 53 Private Hosted Zones are not automatically resolvable by other VPCs unless they are explicitly associated, even across accounts.

Anahtar Kavram

Multi-AZ NAT Gateway routing and cross-account Route 53 Private Hosted Zone association.
Bu soruyu puanla