3 ms·
For the uninformed: AWS has pricing on NAT gateways that can only really be described as predatory. I personally saw a massive bill this year for sending data t
by SOLAR_FIELDS 3y ago
For the uninformed: AWS has pricing on NAT gateways that can only really be described as predatory. I personally saw a massive bill this year for sending data to and from a bucket in the same data center. In other words. I have a service. It’s in us-west-2. I have it sending a bunch of data back and forth between it and a S3 bucket, in the exact same data center. Unless you have some arbitrary checkbox checked in AWS, which absolutely should be checked by default and AWS has no literal reason to have it unchecked bedsides scammy, predatory practices, AWS will send you a massive bill to send bits entirely within their datacenter.
- dartos 3y agoI was speaking with an AWA engineer recently. Apparently most of the AWS services are things that Amazon teams needed and built, which is why the UX and options for them are all over the place. I’d attribute that checkbox to that rather than AWS evil. They also just have 0 incentive it make it better. Third parties like vercel do it for them at a premium.
- SOLAR_FIELDS 3y agoI would normally agree but this has been a known issue for years[0]. It would be trivial for them to change that setting. 0: https://www.lastweekinaws.com/blog/the-aws-managed-nat-gateway-is-unpleasant-and-not-recommended/ https://www.lastweekinaws.com/blog/the-aws-managed-nat-gatew...
- voiceblue 3y agoIt might be “trivial” but in my experience most engineers at these companies are too busy trying to look good in order to either survive the next cut (particularly egregious at Amazon) or get promoted, and fixing this does neither. As Charlie Munger said: show me the incentive, and I’ll show you the outcome.