Compute Savings Plans

AWS Cost Explorer monthly bill breakdown for a Fargate workload showing three cost components: vCPU charges covered by the Compute Savings Plan rate highlighted in green, memory GB-hour charges also covered by the Savings Plan highlighted in green, and a separate Windows OS license fee per-vCPU charge highlighted in orange as not covered by the Savings Plan and billed at full on-demand rate

AWS Compute Savings Plan for Lambda and Fargate: What Is Covered

| | aws, Compute Savings Plans
Most teams buying an AWS Compute Savings Plan are thinking about EC2. They know it covers EC2. What they are less clear on is how it applies to Fargate and Lambda — ...
Usage AI
AWS console showing Compute Savings Plan and EC2 Instance Savings Plan options with hourly commitment input fields.

Compute vs EC2 Instance Savings Plans: Which One Actually Saves More in 2026?

| | Compute Savings Plans, ec2
Compute Savings Plans save up to 66% and cover EC2, Fargate, and Lambda across any region. EC2 Instance Savings Plans save up to 72% but apply only to one instance family in ...
Usage AI
Bar chart diagram showing a single hour of compute usage with the vertical axis representing dollar cost per hour, a horizontal dashed line at the $5 per hour committed amount, the full bar reaching $8 representing total on-demand cost, the lower green portion below the $5 line labeled Savings Plan rate applied at 60 percent discount showing approximate cost of $2 to $2.50, and the upper orange portion above the line representing the remaining $3 billed at standard on-demand rates

How Compute Savings Plans Work (Step-by-Step)

| | Compute Savings Plans, Guides
Most people understand that a Compute Savings Plan saves money on cloud compute. Far fewer understand the precise mechanism — which matters, because getting the commitment amount wrong in either direction costs ...
Usage AI
Coverage comparison diagram split into two panels, the left panel labeled AWS Compute Savings Plan showing EC2, Fargate, and Lambda marked as covered in green and RDS, ElastiCache, DynamoDB marked as not covered in grey, and the right panel labeled Azure Savings Plan for Compute showing Virtual Machines, AKS, Container Instances, App Service, and Azure Functions marked as covered in blue and Azure SQL and Cosmos DB marked as not covered in grey

What Is a Compute Savings Plan?

| | Compute Savings Plans
You already know cloud compute costs money. What you may not realize is how much you are overpaying simply by not committing to it in advance. Cloud providers charge a penalty for ...
Usage AI
AWS Cost Management Savings Plans utilization dashboard showing a 30-day view with the total hourly commitment amount, a pie chart breaking down covered usage by service type with EC2 at 78 percent, Fargate at 14 percent, and Lambda at 8 percent of total covered usage, alongside a utilization trend line showing coverage consistency over time and the percentage of commitment hours that went unused

The Complete Guide to Compute Savings Plans (AWS and Azure)

| | Compute Savings Plans
There is a line on every cloud bill that represents money you paid for capacity you had but did not commit to. It is the gap between your on-demand rate and what ...
Usage AI