Soru

Zorluk: OrtaModernizing Workloads using Containers (ECS and EKS)

A financial technology enterprise, PayGlide, is migrating its legacy payment processing workload from on-premises virtualization hosts to AWS. The workload consists of multiple critical microservices that must be modernized using containers. The enterprise requires a fully managed serverless container platform to eliminate the operational overhead of managing underlying container hosts. The new architecture must span multiple Availability Zones to ensure high availability, and it must have resilient outbound internet access to communicate with external payment gateways. Furthermore, these microservices must resolve the internal DNS names of shared services hosted in a separate shared services VPC within their organization. Which of the following networking and container configurations meets these requirements with the least operational overhead?

  1. A
    Deploy the microservices on Amazon ECS using the AWS Fargate launch type with the `awsvpc` network mode. Deploy a single NAT Gateway in a single public subnet to route outbound traffic for all workload private subnets. Associate the Route 53 Private Hosted Zone of the shared services VPC with the workload VPC.
  2. B
    Deploy the microservices on Amazon ECS using the AWS Fargate launch type with the `bridge` network mode to share the host's network namespace. Deploy redundant NAT Gateways across multiple Availability Zones in the public subnets of the workload VPC. Associate the Route 53 Private Hosted Zone of the shared services VPC with the workload VPC.
  3. Deploy the microservices on Amazon ECS using the AWS Fargate launch type with the `awsvpc` network mode. Deploy redundant NAT Gateways across multiple Availability Zones in the public subnets of the workload VPC. Associate the Route 53 Private Hosted Zone of the shared services VPC with the workload VPC.Cevap
  4. D
    Deploy the microservices on Amazon ECS using the AWS Fargate launch type with the `awsvpc` network mode. Deploy redundant NAT Gateways across multiple Availability Zones in the public subnets of the workload VPC. Route all DNS traffic from the workload VPC to the shared services VPC via an AWS Transit Gateway without associating the Route 53 Private Hosted Zone to the workload VPC.

Cevap

Deploy the microservices on Amazon ECS using the AWS Fargate launch type with the `awsvpc` network mode. Deploy redundant NAT Gateways across multiple Availability Zones in the public subnets of the workload VPC. Associate the Route 53 Private Hosted Zone of the shared services VPC with the workload VPC.
Deploying the containerized microservices on Amazon ECS with the AWS Fargate launch type using the `awsvpc` network mode ensures a serverless compute backend where each task receives its own Elastic Network Interface (ENI). To enable high availability for outbound traffic, NAT Gateways must be deployed in each Availability Zone. For cross-VPC DNS resolution of internal services, the Route 53 Private Hosted Zone from the shared services VPC must be associated with the workload VPC.

Adım Adım Çözüm

1
Select the serverless container execution environment.
Amazon ECS with the AWS Fargate launch type using the `awsvpc` network mode is selected, satisfying the requirement to minimize operational overhead and run on serverless compute.
Fargate eliminates container host management, and it only supports the `awsvpc` network mode.
2
Configure high availability for outbound traffic.
Redundant NAT Gateways are deployed in public subnets across multiple Availability Zones.
This ensures that a failure in one Availability Zone does not disrupt outbound internet access for tasks running in other zones.
3
Configure DNS resolution for the shared services VPC.
The Route 53 Private Hosted Zone of the shared services VPC is associated with the workload VPC.
This allows the Fargate tasks in the workload VPC to resolve internal DNS names of services in the shared services VPC.

Anahtar Kavram

AWS Fargate network mode requirements, multi-AZ outbound routing HA, and Route 53 Private Hosted Zone cross-VPC association.
Bu soruyu puanla