Exam AWS Certified Solutions Architect - Professional topic 1 question 628 discussion

B. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_cannot_pull_image.html

B is the correct answer. The NAT needs to be in public subnet. https://stackoverflow.com/questions/48368499/stopped-cannotpullcontainererror-api-error-500

yes agree, NAT gw always public facing caused need public IP to communicate with ECR Similar question in tutorials Dojos

NAT gateway in the public subnet in the VPC to route requests to the internet.

Agree with B.

B is right When a Fargate task is launched, its elastic network interface requires a route to the internet to pull container images. If you receive an error similar to the following when launching a task, it is because a route to the internet does not exist: CannotPullContainerError: API error (500): Get https://111122223333.dkr.ecr.us-east-1.amazonaws.com/v2/: net/http: request canceled while waiting for connection” To resolve this issue, you can: o For tasks in public subnets, specify ENABLED for Auto-assign public IP when launching the task. o For tasks in private subnets, specify DISABLED for Auto-assign public IP when launching the task, and configure a NAT gateway in your VPC to route requests to the internet.

It's B

Answer is B. NAT gateway should be in the public subnet.

BBB ---

B. NAT gateway needs to be in public subnet.

I go with C For tasks in public subnets, specify ENABLED for Auto-assign public IP when launching the task

I'll go with B

it's B

it's B

going with B

B is my choice

B, NAT GW must in a public subnet in order to work