3 ms·
> And it ended up costing $33 / month just to have a NAT set up to route all of the internet traffic between these services. Yep, this matches my experiences w
by theshrike79 6y ago
> And it ended up costing $33 / month just to have a NAT set up to route all of the internet traffic between these services.
Yep, this matches my experiences with AWS too.
The stuff that you THINK might cost an arm and a leg, are actually really cheap. Billions of lambda calls with thousands running concurrently? meh. Huge SNS/SQS-queues? Meh. Terabytes of data stored in S3? A drop in the bucket.
BUT.
Too many PUT-operations on S3? $$$$$expensive$$$$$ Too much IO on an Aurora instance? Pucker up! Need some sane network configuration? Prepare to pay up the wazoo for gateways.
Yes, all that can be worked around, but it's really non-intuitive to actually see where the pain points in a project will eventually be.