2 ms·
> it's not obvious when you start that a private network has the cost of an NAT GW attached to it It’s not actually required. And I don’t mean the completely
by nucleardog 3y ago
> it's not obvious when you start that a private network has the cost of an NAT GW attached to it
It’s not actually required.
And I don’t mean the completely unrealistic “if you run stuff on your private network that never needs to connect to the internet, then you don’t need a NAT gateway!”. I just mean you can implement routing to the internet in cheaper ways.
If you don’t need 100Gbps highly available outbound traffic routing like a NAT gateway provides… you run a t3.nano instance doing forwarding and NAT that will sustain 30Mbps and burst to 5Gbps for $3.80/mo. Just on raw bandwidth, unless you need more than a t3.large can push (~500Mbps continuous, 5Gbps burst), it’s cheaper to run an EC2 instance as your gateway rather than use a NAT gateway.