NAT Gateway
The ECS Cluster and Service will be deployed in a Private Subnet. During application deployment, we need access to the Public Internet to download public packages hence we will use AWS NAT Gateway which will be deployed in a public subnet with route to route all traffic moving from 0.0.0.0/0 in private subnet to the NAT Gateway.
- Select NAT gateways and click on Create NAT gateway.

- Provide the NAT Gateway name items-server-ngw and select the public subnet in us-east-1a.

- Click on Allocate Elastic IP and click on Create NAT gateway

- Currently in Pending state. Wait till it changes, for about 2 minutes.

- Now the status has changed from Pending to Available.

Now that we have successfully created our NAT Gateway, let's continue by creating the Transit Gateway.