5 ms·
Regarding NAT gateway pricing (~ $30/month or so iirc) we can use a micro (~ $10/month) Linux instance, it's quite literally about 2 commands (sysctl enable ip
by lazyant 5y ago
Regarding NAT gateway pricing (~ $30/month or so iirc) we can use a micro (~ $10/month) Linux instance, it's quite literally about 2 commands (sysctl enable ip forwarding and a masquerade iptables command) or a short script to set it up.
- mwcampbell 5y agoBut that's another thing to keep patched. I wonder if it would be feasible, when using a stripped-down container host OS like Bottlerocket, to configure one container host instance per availability zone to also do NAT. Note that I'm assuming a setup where the containers are running in ECS tasks that use the awsvpc network mode (i.e. each task has its own VPC network interface and private IP address), so security groups can be fine-grained. So even the tasks running on container hosts that do NAT would need the NAT.
- otterley 5y agoAlso, you need to deal with instance failure while minimizing downtime.
- notwedtm 5y agoAlso, NAT gateways don't support TCP or ICMP fragementation. Not always a killer, but when it is, it is.