[Sohcahtoa82]

> If the OpenTTD folks are reading this: this is not true. You can assign public IP addresses to your t4g instances by using a public subnet in the VPC they are deployed to. They will correctly reach WAN addresses via their public interface and you will not need a NAT gateway.

Ah, but putting an EC2 in a public subnet is not "The Way"!

We've let AWS convince us to not put instances in public subnets so that they can make money hand-over-fist on NAT Gateways, which are WAY too expensive for what they are and do.

[devhead]

keeping your servers on the public network is not a good idea for a variety of reasons such as security, cost, control, access and compliance.

AWS makes money, it's a trade off; you can just as well put up an ec2 as a nat that is able to auto scale if you need to give your servers access. or only attach one during updates, etc.

edit: word