Reserve compute capacity with EC2 On-Demand Capacity Reservations
Amazon EC2 Capacity Reservations allow you to reserve compute capacity for your Amazon EC2 instances in a specific Availability Zone for any duration. If you have strict capacity requirements for current or future business-critical workloads that require a certain level of long or short-term capacity assurance, we recommend that you create a Capacity Reservation to help ensure that you always have access to Amazon EC2 capacity when you need it, for as long as you need it.
You can create a Capacity Reservation at any time, and you can choose when it starts. You can request a Capacity Reservation for immediate use or you can request a Capacity Reservation for a future date.
-
If you request a Capacity Reservation for immediate use, the Capacity Reservation becomes available for use immediately and there is no term commitment. You can modify the Capacity Reservation at any time, and you can cancel it at any time to release the reserved capacity and to stop incurring changes.
-
If you request a future-dated Capacity Reservation, you specify the future date at which you need the Capacity Reservation to become available for use. You must also specify a commitment duration for which you commit to keeping the requested capacity in your account after the specified date. At the requested date and time, the Capacity Reservation becomes available for use and the commitment duration starts. During the commitment duration, you can't decrease the instance count or commitment duration below your initial commitment, or cancel the Capacity Reservation. After the commitment duration elapses, you can modify the Capacity Reservation in any way or cancel it if you no longer need it.
Capacity Reservations can only be used by instances that match their attributes. By default, Capacity Reservations automatically match new instances and running instances that have matching attributes (instance type, platform, Availability Zone, and tenancy). This means that any instance with matching attributes automatically runs in the Capacity Reservation. However, you can also target a Capacity Reservation for specific workloads. This allows you to explicitly control which instances are allowed to run in that reserved capacity. You can also specify that instances will only run in a Capacity Reservation or Capacity Reservation resource group.
Important
Future-dated Capacity Reservations are for helping you launch and cover incremental instances, and not to cover existing running instances. If you need to cover existing running instances, use Capacity Reservations that start immediately instead.
Contents
- Concepts for Amazon EC2 Capacity Reservations
- Differences between Capacity Reservations, Reserved Instances, and Savings Plans
- Supported platforms
- Quotas
- Limitations
- Capacity Reservation pricing and billing
- Create a Capacity Reservation
- View the state of a Capacity Reservation
- Launch instances into an existing Capacity Reservation
- Modify an active Capacity Reservation
- Modify the Capacity Reservation settings of your instance
- Move capacity between Capacity Reservations
- Split off capacity from an existing Capacity Reservation
- Cancel a Capacity Reservation
- Capacity Reservation groups
- Create Capacity Reservations in cluster placement groups
- Capacity Reservations in Local Zones
- Capacity Reservations in Wavelength Zones
- Capacity Reservations on AWS Outposts
- Shared Capacity Reservations
- Capacity Reservation Fleets
- Monitor Capacity Reservations usage with CloudWatch metrics
- Monitor Capacity Reservations utilization using EventBridge
- Capacity Reservation utilization notifications from AWS Health
Differences between Capacity Reservations, Reserved Instances, and Savings Plans
The following table highlights key differences between Capacity Reservations, Reserved Instances, and Savings Plans:
| Capacity Reservations | Zonal Reserved Instances | Regional Reserved Instances | Savings Plans | |
|---|---|---|---|---|
| Term | No commitment required for immediate-use Capacity Reservations. They can be created, modified, and canceled as needed. With future-dated Capacity Reservations, you specify a commitment duration for which you commit to keeping the capacity in your account. After the commitment duration elapses, you can cancel the Capacity Reservation at any time. |
Requires a fixed one-year or three-year commitment | ||
| Capacity benefit | Capacity reserved in a specific Availability Zone. | No capacity reserved. | ||
| Billing discount | No billing discount. † | Provides a billing discount. | ||
| Instance Limits | Your On-Demand Instance limits per Region apply. | Default is 20 per Availability Zone. You can request a limit increase. | Default is 20 per Region. You can request a limit increase. | No limit. |
† You can combine Capacity Reservations with Savings Plans or Regional Reserved Instances to receive a discount.
For more information, see the following:
Supported platforms
You must create the Capacity Reservation with the correct platform to ensure that it properly matches with your instances. Capacity Reservations support the following platforms:
-
Linux/UNIX
-
Linux with SQL Server Standard
-
Linux with SQL Server Web
-
Linux with SQL Server Enterprise
-
SUSE Linux
-
Red Hat Enterprise Linux
-
RHEL with SQL Server Standard
-
RHEL with SQL Server Enterprise
-
RHEL with SQL Server Web
-
RHEL with HA
-
RHEL with HA and SQL Server Standard
-
RHEL with HA and SQL Server Enterprise
-
Ubuntu Pro
-
Windows
-
Windows with SQL Server
-
Windows with SQL Server Web
-
Windows with SQL Server Standard
-
Windows with SQL Server Enterprise
When you purchase a Capacity Reservation, you must specify the platform that represents the operating system for your instance.
-
For SUSE Linux and RHEL distributions, excluding BYOL, you must choose the specific platform. For example, the SUSE Linux or Red Hat Enterprise Linux platform.
-
For all other Linux distributions (including Ubuntu), choose the Linux/UNIX platform.
-
If you bring your existing RHEL subscription (BYOL), you must choose the Linux/UNIX platform.
-
For Windows with SQL Standard, Windows with SQL Server Enterprise, and Windows with SQL Server Web, you must choose the specific platform.
-
For all other Windows versions, excluding BYOL which is not supported, choose the Windows platform.
Quotas
The number of instances for which you are allowed to reserve capacity is based on your account's On-Demand Instance quota. You can reserve capacity for as many instances as that quota allows, minus the number of instances that are already running.
Capacity Reservations in the assessing, scheduled, pending ,
active, and delayed state count towards your On-Demand Instance
quota.
Limitations
Before you create Capacity Reservations, take note of the following limitations and restrictions.
-
Active and unused Capacity Reservations count toward your On-Demand Instance limits.
-
Capacity Reservations are not transferable from one AWS account to another. However, you can share Capacity Reservations with other AWS accounts. For more information, see Shared Capacity Reservations.
-
Zonal Reserved Instance billing discounts do not apply to Capacity Reservations.
-
Capacity Reservations can be created in cluster placement groups. Spread and partition placement groups are not supported.
-
Capacity Reservations can't be used with Dedicated Hosts. Capacity Reservations can be used with Dedicated Instances.
-
[Windows instances] Capacity Reservations can't be used with Bring Your Own License (BYOL).
-
Capacity Reservations do not ensure that a hibernated instance can resume after you try to start it.
-
You can request future-dated Capacity Reservations for an instance count with a minimum of 100 vCPUs. For example, if you request a future-dated Capacity Reservation for
m5.xlargeinstances, you must request at least 25 instances (25 * m5.xlarge = 100 vCPUs). -
You can request future-dated Capacity Reservations for instance types in the C, I, M, R, or T instance families only.
