Difficult cost tracking and hidden billing charges
8/10 HighAWS billing is opaque and difficult to track. Hidden charges from services like EBS snapshots, NAT gateways, and Route 53 are hard to identify. Billing alerts arrive before invoices are sent, and AWS's pay-per-use model makes experimentation risky without proper monitoring.
Sources
- How Stripe Put Developers First and Reshaped Online Payments
- Why is AWS Complicated for Devs? Understanding Major ...
- Major AWS Challenges and How to Overcome Them - KnowledgeHut
- Ask HN: Things you like or dislike about using AWS
- What are some common challenges faced by AWS Developers?
- Amazon Simple Storage Service (S3) Reviews & Product Details
- 5 Common Mistakes to Avoid When Using AWS S3 - GeeksforGeeks
Collection History
Pricing can also be hard to reason about. Beyond the headline transaction fee, businesses run into add-ons (billing, fraud tools, tax, currency conversion) and edge cases (refunds, disputes, payout timing).
The pricing model, while flexible, can be confusing—especially when dealing with multiple storage classes, data retrieval fees, and transfer costs... Pricing can get complicated for large-scale deployments, particularly when there are frequent data transfers and retrievals.
There is no truly safe way to experiment and play around, even in the free tier. I set up billing alerts, but even with that it can be tricky to identify exactly what is costing me money (EBS snapshots, NAT gateways, Route 53 hosted zones, etc)