4 ms·
Hijaking this to say I hate VPC. I hate VPC. Applying 1990s NATting to next gen cloud service? Gotta give the greybeards something to do. The purpose of NATti
by paulddraper 5y ago
Hijaking this to say I hate VPC. I hate VPC.
Applying 1990s NATting to next gen cloud service? Gotta give the greybeards something to do.
The purpose of NATting is to deal with limited IP addresses, a problem that has been solved for a long time now.
AWS makes me create a VPC, but I certainly don't set up some central-point-of-failure NAT or pay AWS to do it.
- res0nat0r 5y agoAre you talking about instances you want completely isolated with no public IP addresses and only RFC1918 IP's, but can reach out to the internet? Nat Gateway has been around for ~6 years now and is highly available and a managed service so you just need to click a couple of buttons. https://aws.amazon.com/about-aws/whats-new/2015/12/introducing-amazon-vpc-nat-gateway-a-managed-nat-service/ https://aws.amazon.com/about-aws/whats-new/2015/12/introduci...
- wyldfire 5y agoThis is probably dismissed by the "or pay AWS to do it" clause.
- mwcampbell 5y agoAt $0.045/hour, NAT gateways are expensive. This sets up perverse incentives, as it's cheaper to keep wasting public IPv4 addresses. If anyone from AWS is watching, I suggest that you make the base fixed price of NAT gateways way cheaper, and maybe add a small extra charge for EC2 instances and Fargate tasks with public IPs.
- orf 5y agoIt’s $30 per month, which is not expensive and is gonna be a rounding error to most users.
- terom 5y agoYou need one of those per AZ, and multiples of that if you split up projects across VPCs or AWS accounts. AWS accounts and VPCs are free, so NAT gateways can form a significant part of the per-account/VPC base cost, which can be a significant part of your total cost for a small project/environment.
- paulddraper 5y agoYes, I get to pay AWS $30/month per VPC for immense privileged of accessing the internet from my cloud VPS.
- rswail 5y agoThe only problem with NAT gateways is that they are single-AZ. So if you're setting up multi-AZ in a VPC, you need one per AZ and you need the routing to be AZ specific. If the NAT gateway was a service, then it could be multi-AZ transparent to the VPC.
- jlawer 5y agoExcept with IPv4... it hasn't been solved because there just isn't enough addresses. And most organisations I have worked with on AWS is still predominately IPv4.
- wmf 5y agomost organisations I have worked with on AWS is still predominately IPv4. Because AWS initially had poor IPv6 support and they didn't include it as "cloud native". Customers build things the way AWS encourages them to.
- 1123581321 5y agoIf VPC isn’t important to you, haven’t you made one catch-all VPC for your account a long time ago with good-enough general settings? It shouldn’t come up that often unless you are in a position to benefit from the feature.
- paulddraper 5y agoYes I have. But I also work with a lot of people that don't.
- rswail 5y agoAWS does that for you by auto setting up a default VPC in each region.
- rhacker 5y agoThe fact that we have NATting is why you still have ipv4 addresses at all. Just look at the other thread about ipv6 that's going on in HN right now. Even if a small percent of a population doesn't have an IPv6 address means that no company can use it exclusively yet.
- wmf 5y agoIPv6-only VPC with dual-stack load balancers seems like it would be a great architecture if cloud providers would dot all the i's to make it happen. https://www.internetsociety.org/resources/deploy360/2014/case-study-facebook-moving-to-an-ipv6-only-internal-network/ https://www.internetsociety.org/resources/deploy360/2014/cas... https://toreanderson.github.io/2016/02/22/ipv6-only-data-centre-rfcs-published.html https://toreanderson.github.io/2016/02/22/ipv6-only-data-cen...
- mwcampbell 5y agoBut would such a VPC be able to make outgoing connections to IPv4-only servers?
- wmf 5y agoYou could use a NAT64 gateway to do that. At that point you're trading one form of NAT for another so there's less value in going IPv6-only.
- floatboth 5y agoWell not having to dualstack is still just nice. No more DHCP4, and so on – e.g. you can have SLAAC as the one and only very simple way of auto-assigning addresses (in a client setting, obviously not what you'll use with servers that have their addresses listed in DNS :D)
- carlhjerpe 5y agoIt would be nice if NAT64 was embraced everywhere, I love typing IP addresses because I'm lazy, but we need IPv6 right now. There are still too many rough edges going V6 only though, like if I set my own DNS servers, will they resolve A records to NAT64 AAAA records? And how will the regular Windows sysadmin deal with registering DNS records?
- lowbloodsugar 5y agoWhy would you think its 1990s NAT? Launch an instance with a public IP and there's no central-point-of-failure. The "Internet Gateway" isn't an actual physical device.
- rswail 5y agoThe IGW is not the NAT gw. You need both for private networks outgoing public connections.
- lowbloodsugar 5y agoSure. It's not the NAT gw. But it is NAT. Op was complaining about having to use 1990s NAT, and I was responding to that. NAT gw isn't really 1990s NAT either, since it autoscales. I assume the sentiment was the complaint about having a "public" subnet and a "private" subnet, and using a NAT to route traffic for the "private" subnet. Its been a while since I used AWS, but I was at a large company and that's simply how IT Security demanded it. So, of course, AWS offers a solution for that market. But if you use IGW, then your "public" subnet is still actually a private subnet: all networking to hosts inside the VPC occurs with private IPs. The public IPs are 1:1 NATed by the IGW. Your instances never see packets with their public IP. And you can launch instances in the "public" subnet without a NAT mapping if you want. For IPv6, you can have an egress only IGW. So you can do "traditional" NAT if you want, or you can do "modern cloud" NAT using IGW. It is really your choice. I'm not saying one is better than the other. I'm just letting OP know that there is a non-1990s option. =)
- hrez 5y agoExcept you don't need NAT. You don't even have to get external ipv4. Use ipv6 for external ip and internet access. Think of it as classic with customizable internal network. VPC is a superset of classic.
- staticassertion 5y ago> The purpose of NATting is to deal with limited IP addresses, a problem that has been solved for a long time now. You mean by nat'ing?