4 ms·

Anyone else find it somewhat baffling that it's taken until now for a NAT service to arrive on AWS? I'm happy to have it available of course, definitely not go

by benley 11y ago

Anyone else find it somewhat baffling that it's taken until now for a NAT service to arrive on AWS? I'm happy to have it available of course, definitely not going to complain. I've just long wondered why it wasn't a thing since the early days of VPC.

Rapzid 11y ago
I find this pretty typical of AWS TBH. You could ask the similar questions about other service like: Why can I make IAM policies for EC2 that key in on tags, but not other services? Why can I filter on tag for some resources in the console but not all? Why don't ALL resources support tags?! IAM would be way less of a PITA if you could put resources into groups.. Hey, if they had tag support for all of their resources and you could restrict access to them like ec2 that would be like resource groups... Why can't I pay more to just scale ELB's up? Why don't ELB's support connection draining...(this has been addressed but was the most complained about ELB shortcoming for a long time). Etc. Etc. Etc. But hey, things are not so bad and have really improved quite a bit in all fairness.
cheeseprocedure 11y ago
I wonder the same, though the engineering under the hood is more interesting than I thought: http://perspectives.mvdirona.com/2015/12/vpc-nat-gateways-transactional-uniqueness-at-scale/ http://perspectives.mvdirona.com/2015/12/vpc-nat-gateways-tr... > The connections are managed by a fault-tolerant co-operation of devices in the VPC network fabric. Each new connection is assigned a port in a robust and transactional way, while also being replicated across an extensible set of multiple devices. In other words: the NAT gateway is internally horizontally scalable and resilient. Maybe it just wasn't a priority.
- hrez 11y ago
  So it's very similar to VPC Internet Gateway, only with upcharge of $0.045/Gb on traffic.
joesmo 11y ago
You mean AWS ignores basic infrastructure components in favor of more glamorous ones? Never! </sarcasm>

by benley 11y ago

Rapzid 11y ago

I find this pretty typical of AWS TBH. You could ask the similar questions about other service like: Why can I make IAM policies for EC2 that key in on tags, but not other services? Why can I filter on tag for some resources in the console but not all? Why don't ALL resources support tags?! IAM would be way less of a PITA if you could put resources into groups.. Hey, if they had tag support for all of their resources and you could restrict access to them like ec2 that would be like resource groups... Why can't I pay more to just scale ELB's up? Why don't ELB's support connection draining...(this has been addressed but was the most complained about ELB shortcoming for a long time). Etc. Etc. Etc. But hey, things are not so bad and have really improved quite a bit in all fairness.

cheeseprocedure 11y ago

I wonder the same, though the engineering under the hood is more interesting than I thought: http://perspectives.mvdirona.com/2015/12/vpc-nat-gateways-transactional-uniqueness-at-scale/ http://perspectives.mvdirona.com/2015/12/vpc-nat-gateways-tr... > The connections are managed by a fault-tolerant co-operation of devices in the VPC network fabric. Each new connection is assigned a port in a robust and transactional way, while also being replicated across an extensible set of multiple devices. In other words: the NAT gateway is internally horizontally scalable and resilient. Maybe it just wasn't a priority.

hrez 11y ago
So it's very similar to VPC Internet Gateway, only with upcharge of $0.045/Gb on traffic.

joesmo 11y ago

You mean AWS ignores basic infrastructure components in favor of more glamorous ones? Never! </sarcasm>