Cloud concept · Updated

Commitment Discounts - Commitment discounts reduce cloud usage rates in exchange for a defined usage or spending commitment over a fixed term.

In short

Cloud providers offer lower rates when customers commit to eligible resource usage or spending, commonly for one or three years. These discounts can reduce the cost of predictable workloads, but unused commitments can offset or eliminate the savings.

Cloud Concepts Hub →

6 key aspects of Commitment Discounts

Effective commitment purchasing balances lower rates against forecast risk, eligibility restrictions, and the continuing obligation to pay.

01
A defined obligation for a lower rate

The customer commits to eligible usage or spending for a fixed term in exchange for discounted pricing. Evaluate the total obligation, not just the advertised percentage reduction.

02
Best suited to a predictable baseline

Size commitments around sustained demand that is likely to remain after rightsizing and planned migrations. Use more flexible purchasing options for uncertain demand and temporary peaks.

03
Eligibility and flexibility have boundaries

Discounts apply only to usage that matches the offering's rules, which can involve service, Region, instance family, tenancy, or other attributes. Broader applicability can reduce the risk that architecture changes leave a commitment unused.

04
Discounts and capacity are separate

A billing commitment does not automatically guarantee resource availability. Select a capacity reservation separately when required, unless the chosen offering explicitly includes that benefit.

05
Unused commitments reduce realized savings

A commitment remains payable even when matching usage falls below the purchased amount. Monitor utilization and coverage together, and reassess expected demand before adding or renewing commitments.

06
Purchasing options can be combined

Use commitments for stable workloads, On-Demand purchasing for flexibility, and Spot capacity for interruption-tolerant work. Choose dedicated hardware for isolation or licensing needs rather than assuming it is a discount mechanism.

Cloud services for Commitment Discounts

EC2, Fargate, and Lambda provide different ways to run applications, while Savings Plans can apply commitment discounts to eligible usage across these services. EC2 Reserved Instances provide another route for workloads that match their eligibility rules. An organization can cover a stable compute baseline with commitments while leaving uncertain demand on standard pricing and using EC2 Spot for interruption-tolerant work. Capacity Reservations and dedicated tenancy should be evaluated separately for availability, isolation, and licensing requirements. Across the portfolio, monitor eligible spending, commitment utilization, and coverage rather than assuming that every compute charge is discounted.

Amazon EC2Amazon EC2

EC2 supports Reserved Instances and eligible Savings Plans benefits for committed usage, alongside On-Demand and Spot purchasing. It also provides dedicated tenancy and capacity reservation options, which address requirements distinct from discounted pricing.

Savings PlansSavings Plans

Savings Plans provide discounted rates in exchange for a consistent amount of eligible hourly spending over a one- or three-year term. The selected plan determines which usage qualifies; unused hourly commitment does not roll over to later hours.

AWS FargateAWS Fargate

Eligible Fargate usage can receive Compute Savings Plans discounts. This allows an organization to cover a predictable container-compute baseline without committing to specific EC2 instances.

AWS LambdaAWS Lambda

Eligible Lambda duration and Provisioned Concurrency charges can receive Compute Savings Plans discounts. Lambda request charges are not covered, so engineers must distinguish eligible compute spending from the total function bill.

Commitment Discounts exam questions

Real practice exam questions on Commitment Discounts, with the correct answer and its explanation. Answer them with every option in the exam simulator.

CLF-C02

A company runs production applications continuously on Amazon EC2. For the next year, all instances will remain in the m7i instance family in one AWS Region, but the company expects to change instance sizes and operating systems. The company can commit to a consistent amount of hourly spending, and its applications cannot tolerate Spot interruptions. Which purchasing option provides the greatest discount potential while preserving the flexibility the company needs?

Show answerCORRECT ANSWER

A one-year EC2 Instance Savings Plan for m7i in the selected Region

An EC2 Instance Savings Plan offers lower prices in exchange for an hourly spending commitment for a selected instance family in one Region. Its discounts apply across instance sizes and operating systems within that scope, providing the required flexibility with greater discount potential than a Compute Savings Plan.

MLA-C02 (beta)

A company runs a CPU-based ML inference application on Amazon EC2. During the next year, the company will move some inference components to AWS Fargate and lightweight preprocessing functions to AWS Lambda. The remaining EC2 components might change instance families and AWS Regions. Cost analysis confirms that the application's aggregate eligible compute spending will remain above a conservative hourly commitment throughout the year. The company wants to start reducing compute costs immediately and retain the discounts as the migration proceeds, without modifying the migration plan. Which purchasing strategy best meets these requirements?

Show answerCORRECT ANSWER

Purchase a one-year Compute Savings Plan based on the conservative hourly spending commitment.

Compute Savings Plans cover eligible EC2, Fargate, and Lambda usage. Their EC2 coverage is flexible across instance families and Regions, so the discounts can follow this application's migration. The validated hourly spending floor supports a commitment without relying on uncertain future demand.

SAP-C03

A company operates a rightsized fleet of Amazon RDS for PostgreSQL databases. During the next 12 months, teams will migrate some workloads to Aurora Serverless v2 and move others between AWS Regions. The migration schedule and final allocation of workloads are uncertain, but the aggregate database demand is predictable.

A pricing analysis that accounts for all planned migrations establishes the following usage throughout the next year:
• For 18 hours each day, eligible database usage costs $60 per hour at On-Demand rates or $40 per hour at the applicable discounted commitment rates.
• For the remaining 6 hours each day, eligible usage costs $120 per hour at On-Demand rates or $80 per hour at the applicable discounted commitment rates.

All planned database configurations are eligible for the applicable database commitment offering. The company has no existing reservations or spending commitments. Finance requires any new hourly commitment to be fully consumed in every hour, including during migrations. The company must preserve flexibility to change database engines, capacity configurations, and Regions.

Which purchasing strategy provides the greatest commitment-based savings while meeting these requirements?

Show answerCORRECT ANSWER

Purchase a one-year Database Savings Plan with a $40-per-hour commitment. Allow eligible usage above the commitment to be billed at On-Demand rates.

Database Savings Plans provide flexibility across eligible database services, engines, capacity configurations, and Regions. The commitment is consumed at Savings Plans rates, so $40 per hour is the largest commitment that the established baseline will fully consume every hour. Usage beyond the commitment remains On-Demand.

Practice Commitment Discounts in a full exam

Questions on Commitment Discounts in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Commitment Discounts

3 min read

Commitment discounts exchange purchasing flexibility for a lower unit price. Instead of paying only the standard on-demand rate for resources as they run, an organization accepts a defined financial obligation over a term. The commitment may cover particular resource characteristics or a specified amount of eligible spending per hour. The central decision is whether future usage is predictable enough to justify that obligation.

In the cloud, commitments generally operate as billing arrangements rather than instructions to deploy resources. Eligible usage receives the discounted rate according to the agreement's matching rules. A commitment does not necessarily create a virtual machine, keep an application running, or guarantee that capacity will be available. Resource deployment, billing discounts, and capacity assurance are separate concerns, although some purchasing options combine them.

AWS illustrates two common approaches. Amazon EC2 Reserved Instances provide billing benefits for matching EC2 usage, with applicability determined by attributes and offering rules. AWS Savings Plans instead require a consistent amount of eligible hourly spending for one or three years. Compute Savings Plans can apply across eligible EC2, AWS Fargate, and AWS Lambda usage, while EC2 Instance Savings Plans are tied to an instance family in a selected Region. Neither model means that every charge on the account receives a discount.

Consider an application that continuously needs ten virtual machines but scales to thirty during business peaks. An engineer might purchase commitments for a conservative portion of the ten-machine baseline, retain On-Demand capacity for uncertain growth, and use Spot capacity for interruptible background processing. Committing to the peak would leave part of the obligation unused during quieter hours. Rightsizing resources and removing idle workloads before purchasing commitments reduces this risk.

On-Demand purchasing is useful for short-lived workloads, experimentation, and demand that cannot yet be forecast. It avoids a long-term commitment but normally has a higher unit rate than comparable committed usage. Spot Instances use spare EC2 capacity at discounted prices and can be interrupted; their discount is not earned through a long-term commitment. They fit workloads such as checkpointed batch processing, not applications that cannot tolerate interruption without additional resilience.

Capacity Reservations address a different requirement: access to EC2 capacity in a particular Availability Zone. An On-Demand Capacity Reservation does not itself provide a commitment discount, although eligible Reserved Instance or Savings Plans benefits can apply to its charges. Regional EC2 Reserved Instances provide a billing discount without reserving capacity; zonal EC2 Reserved Instances can also provide a capacity reservation for matching attributes. Exam questions often test this distinction between reducing price and assuring capacity.

Dedicated Hosts and Dedicated Instances primarily address hardware isolation, compliance, or licensing requirements rather than commitment discounts. A Dedicated Host provides a physical server dedicated to a customer, with host-level visibility and placement control. Dedicated Instances run on hardware isolated from other customers but do not provide the same host-level control. Dedicated Host Reservations can reduce eligible host costs through a term commitment; choosing dedicated tenancy alone does not create a commitment discount.

Payment schedules and commitment obligations must also be distinguished. All-upfront, partial-upfront, and no-upfront options may be available depending on the offering, but no upfront payment does not mean no commitment. Stopping resources generally does not stop the financial obligation. Engineers should track utilization, meaning how much purchased commitment is consumed, and coverage, meaning how much eligible usage receives a discount. High coverage is not a success if excessive commitments remain unused.

Learn Commitment Discounts in lessons

8 short lessons on Commitment Discounts in 4 certification courses.

and 2 more lessons

Open the lessons