7 comments

  • ecesena 17 hours ago ago

    If cost is the main issue, could you route all instances through a single nat, instead of one per AZ?

  • spaceprison 2 days ago ago

    You’ll need a vpc subnet connected “something” with outbound access.

    Natgw and nat instance are about all there is or something crazy like a site to site vpn attached to your vgw and a server/firewall outside of aws/ec2 connected to the internet acting like a router…?

    • nodesocket 2 days ago ago

      Thanks, figured as much. AWS hasn't lowered the price of NAT gateways in (ever) I think. It's a bit absurd seeing as the dramatic price reduction of Graviton based instances and such. NAT gateways should be like 1/2 or 1/3 the current cost.

  • somedanishguy 2 days ago ago

    I can only recommend fck-nat.dev as an alternative to aws’s own nat instances.

    • romanhn a day ago ago

      Fck-nat is great, and I'm running it for the exact same reason that the NAT Gateway is expensive for my hobby project. I configured it with an auto scaling group to bring it back up if the instance dies. The instance doubles as a bastion host as well.

    • nodesocket 2 days ago ago

      Awesome, will look at deploying fck-nat.dev. Love the name. So absurd AWS hasn’t updated their NAT instance AMI since 2018 and running Amazon Linux v1 which is end of life.

  • samcat116 2 days ago ago

    The ideal answer is IPv6 subnet with an egress only internet gateway