[outworlder]

Not OP but I'll add:

AWS can only have a single NAT gateway per subnet/availability zone(they are usually added in the route table as 0.0.0.0/0). Nat GWs can only scale up so much. If we blow past the limits, then the only option is to use resources from a different subnet. I realize things cannot scale vertically forever, but the fact that one can scale horizontally (by adding more NAT GWs in different subnets) tells me that there could be an architecture that would make this a non-issue to customers.

Also if a NAT Gateway has issues (see the outage on Aug 31st) we, the customers, have to figure out how to route around it.

In Google Cloud you can (easily) add multiple NAT gateways as your requirements grow, while staying in the same subnet. Not sure how far one can go (didn't go past 20 Nat GWs or so). We still have to worry about that (specially since in GCP the number of allowed connections is much smaller), ideally we shouldn't have to worry about this either :)

Azure does not have the same concept because they are bonkers (outgoing traffic goes out of your load balancer (?!))

[matsur]

Are you running TCP/UDP workloads or is NAT for any IP protocol needed?