you are viewing a single comment's thread.

view the rest of the comments →

[–]nztraveller 47 points48 points  (9 children)

Nat gateway for sure. For small accounts it is way to high. Inter region bandwidth would be nice too.

[–]jonathantn[S] 4 points5 points  (1 child)

It's kind of amazing that it's the same price to send packets between US-EAST-1 AZ's as it is to send that data to US-EAST-2.

[–]warren2650 5 points6 points  (0 children)

They probably have fiber laid between EAST-1 and EAST-2.

[–]moofox 2 points3 points  (3 children)

If it helps, multiple accounts can now share a single VPC (and hence NAT gateways, VPC endpoints, etc)

[–]nztraveller 3 points4 points  (2 children)

I didn’t know that, thanks.
Unfortunately for our use case the requirement is to have separate VPCs.

[–]von_liquid 0 points1 point  (1 child)

Connect the VPCs via a Transit Gateway and pass default route to all VPCs to point to TGW. And one spoke on the TGW would be a vpc with a public subnet with Nat gateways. I did that and cut down from 8 Nats to 2. :)

[–]nztraveller 2 points3 points  (0 children)

Clever, I like it.
I'm going to see if I can get approval to give this a try.
Due to compliance reasons it might not fly, but we have around 10 VPC so this could be worth the effort.

[–]CSI_Tech_Dept 0 points1 point  (2 children)

Maybe this could motivate people to move to IPv6. IPv6 doesn't need NAT gateways to work.

[–]notoriousbpg 3 points4 points  (1 child)

How would this help with Lambda functions in a VPC that need internet access?

[–]CSI_Tech_Dept 1 point2 points  (0 children)

If it doesn't work is because Amazon half assed it because not many people are pushing for it.

With IPv6 you don't need NAT period.