AWS storage, data, and network.
Storage and network charges are the plaque of an AWS account: they accumulate slowly, nobody feels them day to day, and by the time someone looks, they are 30 percent of the bill. Snapshots outlive the volumes they protect, S3 buckets never meet a lifecycle policy, and cross-AZ traffic quietly doubles the cost of chatty architectures. This hub covers the mechanisms and the cleanup order.
26 articles
Every article in this hub.
BlogAthena and Query Cost DisciplineBackup Policies That Do Not Bankrupt YouBedrock and GenAI Spend on AWSCloudFront Economics for Heavy EgressCloudWatch Logs: The Quiet Budget EaterCross Region Replication CostsData transfer between AZs and regionsDecommissioning AWS Data You No Longer NeedDynamoDB on demand versus provisionedEBS snapshots and the cost of forgettingEFS versus EBS versus S3 on costGlacier and Deep Archive EconomicsIntelligent Tiering: When It Pays OffKinesis and Streaming Cost ControlNAT Gateway Costs and the AlternativesNetwork architecture choices that cut the AWS billRedshift Cost Optimization in PracticeS3 cost optimization end to endS3 request costs people forgetS3 storage classes and lifecycle policiesSageMaker Cost Control for ML TeamsStorage tagging and ownershipThe AWS Storage Review PlaybookThe Economics of AWS Data LakesVPC endpoints as a cost move
Related
Related topic hubs.
Independent · buyer-side
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data.