Re:AWS to Begin Charging for Public IPv4 Addresses
by dwilkie on Thursday August 03, 2023 @09:26PM
(#36994297)
You don’t actually need to use the AMI. Here’s an example of a NAT instance we build from scratch:
https://github.com/somleng/somleng-project/blob/main/infrast...
Re:AWS to Begin Charging for Public IPv4 Addresses
by ttt3ts on Thursday August 03, 2023 @09:00PM
(#36994119)
Thanks! That is exactly what I wanted to know.
Re:AWS to Begin Charging for Public IPv4 Addresses
by endgame on Thursday August 03, 2023 @09:02PM
(#36994144)
Another thing: EC2 instances (VMs) have a "Source/Destination IP check" which makes them ignore any packets not intended for them. If you want an instance to do NAT, you need to turn this off.
https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Ins...
I say sorta because it's built on an old version of Amazon Linux and is headed towards EOL with no replacement except "go build your own" as you suggest.
https://www.lastweekinaws.com/blog/an-alternat-future-we-now...
AlterNAT uses managed NAT Gateways as a fallback when the NAT Instance is out of service, but again you will have to make your own NAT AMI.
This is not to excuse AWS' frankly absurd NATGW pricing, but to point out other ways around it.