Timeline for Why do I need a Nat Gateway for ECS containers using AWSVPC?
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 10, 2021 at 12:59 | answer | added | chronicc | timeline score: 1 | |
Jan 18, 2021 at 13:45 | vote | accept | mega6382 | ||
Jul 21, 2020 at 4:04 | comment | added | Juraj Martinka | One issue with NAT Gateway is that you are charged for inbound data transfer which is unlike Internet gateway or plain old EC2 instance where you don't pay anything for inbound traffic. It might come as a surprise later when you scale up your service. | |
Jul 19, 2020 at 6:27 | answer | added | Kaymaz | timeline score: 3 | |
Jul 17, 2020 at 19:52 | comment | added | mega6382 | @WoodlandHunter but is it possible to use AWSVPC network type and still run the containers in public subnet? | |
Jul 17, 2020 at 19:51 | comment | added | mega6382 | @WoodlandHunter thanks, I will check those links. | |
Jul 17, 2020 at 19:50 | comment | added | mega6382 | @WoodlandHunter I am using ec2 with autoscalling group. | |
Jul 17, 2020 at 16:40 | comment | added | Woodland | For the record, it is entirely possible to run containers in a public subnet, and we can help you configure that, but it is best-practice to use a setup like VPC Scenario 2: docs.aws.amazon.com/vpc/latest/userguide/VPC_Scenario2.html A brief explanation of why can be found in this doc: docs.aws.amazon.com/quickstart/latest/vpc/architecture.html | |
Jul 17, 2020 at 16:26 | comment | added | Woodland | What is your task networking mode? Are you running on EC2 or Fargate? docs.aws.amazon.com/AmazonECS/latest/developerguide/… | |
Jul 17, 2020 at 13:51 | review | First posts | |||
Jul 17, 2020 at 19:49 | |||||
Jul 17, 2020 at 13:49 | history | asked | mega6382 | CC BY-SA 4.0 |