# Reserve compute capacity with EC2 On-Demand Capacity Reservations 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 charges. + 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. All supported Amazon EC2 instances with matching attributes, that is instance type, platform, Availability Zone, and tenancy, are eligible to run in a Capacity Reservation. The Amazon EC2 instance can be launched by you (*non-managed instances*) or on your behalf by an AWS service (*managed instances*). This is particularly true for *open* Capacity Reservations, which automatically match with any running instances that have matching attributes. For example, managed instances launched on your behalf by the following services are eligible to run in Capacity Reservations that you create and manage. + Amazon EC2 Auto Scaling + Amazon ECS + Amazon EKS + Amazon EMR + Amazon SageMaker AI + AWS Batch + AWS Elastic Beanstalk + AWS ParallelCluster + AWS Parallel Computing Service (AWS PCS) **Topics** + [ # Concepts for Amazon EC2 Capacity Reservations ](cr-concepts.md) + [ ## Differences between Capacity Reservations, Reserved Instances, and Savings Plans ](#capacity-reservations-differences) + [ ## Supported platforms ](#capacity-reservations-platforms) + [ ## Quotas ](#capacity-reservations-limits) + [ ## Limitations ](#capacity-reservations-limitations) + [ # Capacity Reservation pricing and billing ](capacity-reservations-pricing-billing.md) + [ # Create a Capacity Reservation ](capacity-reservations-create.md) + [ # View the state of a Capacity Reservation ](capacity-reservations-view.md) + [ # Launch instances into an existing Capacity Reservation ](capacity-reservations-launch.md) + [ # Modify an active Capacity Reservation ](capacity-reservations-modify.md) + [ # Modify the Capacity Reservation settings of your instance ](capacity-reservations-modify-instance.md) + [ # Move capacity between Capacity Reservations ](capacity-reservations-move.md) + [ # Split off capacity from an existing Capacity Reservation ](capacity-reservations-split.md) + [ # Cancel a Capacity Reservation ](capacity-reservations-release.md) + [ # Use Capacity Reservations with cluster placement groups ](cr-cpg.md) + [ # Capacity Reservation groups ](create-cr-group.md) + [ # Capacity Reservations in Local Zones ](capacity-reservations-localzones.md) + [ # Capacity Reservations in Wavelength Zones ](capacity-reservations-wavelengthzones.md) + [ # Capacity Reservations on AWS Outposts ](capacity-reservations-outposts.md) + [ # Shared Capacity Reservations ](capacity-reservation-sharing.md) + [ # Capacity Reservation Fleets ](cr-fleets.md) + [ # Monitor Capacity Reservations usage with CloudWatch metrics ](capacity-reservation-cw-metrics.md) + [ # Monitor Capacity Reservation underutilization ](cr-eventbridge.md) + [ # Monitor state changes for future-dated Capacity Reservations ](monitor-fcr-state.md) + [ # Interruptible Capacity Reservations ](interruptible-capacity-reservations.md) # Concepts for Amazon EC2 Capacity Reservations Concepts The following key concepts apply to Capacity Reservations. **Topics** + [ ## Start date and time ](#cr-start-date) + [ ## End date and time ](#cr-end-date) + [ ## Commitment duration ](#cr-commitment-duration) + [ ## Future-dated Capacity Reservation assessment ](#cr-future-dated-assessment) + [ ## Capacity Reservation attributes ](#cr-attributes) + [ ## Instance matching criteria ](#cr-instance-eligibility) ## Start date and time The start date and time defines when the Capacity Reservation becomes available for use. A Capacity Reservation can start **immediately**, or it can start at a **future date**. + If you choose to start a Capacity Reservation immediately, the reserved capacity becomes available for use immediately after you create it, and billing starts as soon as the Capacity Reservation enters the active state. You do not need to enter into any term commitments. You can modify the Capacity Reservation as needed at any time to meet your needs, and you can cancel it at any time to release the capacity and to stop incurring charges. + If you choose to start a Capacity Reservation at a future date, you specify a *future date and time* at which you will need the reserved capacity, and a *commitment duration*, which is the minimum duration for which you commit to keeping the requested Capacity Reservation in your account after it has been provisioned. At the specified future date, the Capacity Reservation becomes available for use and billing starts at that time, once the Capacity Reservation enters the active state. The commit duration starts as soon as the Capacity Reservation is provisioned in your account. During this time, you can't decrease the instance count below the committed instance count, choose an end date that is before the commitment duration, or cancel the Capacity Reservation. However, after the commitment duration lapses, you are free to modify the Capacity Reservation in any way, or cancel it to release the reserved capacity and to stop incurring charges. ## End date and time The end date and time defines when the Capacity Reservation ends and the reserved capacity is released from your account. You can configure a Capacity Reservation to **end automatically** at a specific date and time, or you can configure it to stay active indefinitely until you ** manually cancel it**. If you configure a Capacity Reservation to end automatically, the Capacity Reservation expires within an hour of the specified time. For example, if you specify `5/31/2019, 13:30:55`, the Capacity Reservation is guaranteed to end between `13:30:55` and `14:30:55` on `5/31/2019`. After a reservation ends, the reserved capacity is released from your account and you can no longer target instances to the Capacity Reservation. Instances running in the reserved capacity continue to run uninterrupted. If instances targeting a Capacity Reservation are stopped, you can't restart them until you remove their Capacity Reservation targeting preference or configure them to target a different Capacity Reservation. For more information, see [Modify the Capacity Reservation settings of your instance](capacity-reservations-modify-instance.md). ## Commitment duration The commitment duration applies to future-dated Capacity Reservations only. The commitment duration is a minimum duration for which you commit to having the future-dated Capacity Reservation in the active state in your account after it has been provisioned. You can keep a future-dated Capacity Reservation for longer than the commitment duration, but not shorter. The following apply during the commitment duration: + You can't cancel a Capacity Reservation during the commitment duration. + You can't decrease the instance count below the committed instance count, but you can increase it. + You can't configure a Capacity Reservation to automatically end at a date or time that is within the commitment duration. You can extend the end date and time during the commitment period. Amazon EC2 uses the commitment duration that you specify to assess whether the request can be supported. The minimum commitment duration is 14 days. While assessing a request, Amazon EC2 might determine that it can support a shorter commitment duration. In that case, Amazon EC2 will schedule the future-dated Capacity Reservation with the shorter commitment duration. This means that you are committed to keeping the Capacity Reservation in your account for a shorter period than you initially requested. ## Future-dated Capacity Reservation assessment When you request a future-dated Capacity Reservation, Amazon EC2 assesses the request to determine whether it can be supported based on capacity availability and the commitment duration you specify. The assessment is typically completed within 5 days. Amazon EC2 considers multiple factors when evaluating a request, including: + Forecasted capacity supply + The commitment duration + How early you request the Capacity Reservation relative to your start date + The size of your request You can request a future-dated Capacity Reservation between 5 and 120 days in advance. We recommend that you make the request at least 56 days (8 weeks) in advance to improve our ability to support your request. The minimum commitment duration is 14 days and the minimum instance count is 32 vCPUs. The Capacity Reservation remains in the `assessing` state while the request is being assessed. If the request can be supported, the Capacity Reservation enters the `scheduled` state and it is scheduled for delivery on the requested date and time. The total instance count remains 0 during while the Capacity Reservation is in the `scheduled` state. A scheduled Capacity Reservation will become `active` and available for use at the requested date. If a request can't be supported, the Capacity Reservation enters the `unsupported` state. Unsupported Capacity Reservations are not delivered. You can cancel a future-dated Capacity Reservation while it is in the `assessing` state. For more information, see [Create a future-dated Capacity Reservation](capacity-reservations-create.md#create-future-cr). ## Capacity Reservation attributes When you create a Capacity Reservation, you must specify the following attributes: + Availability Zone + Instance type + Platform (operating system type) + Tenancy (`default` or `dedicated`) Only instances that match these attributes can launch or run in the Capacity Reservation. ## Instance matching criteria Instance matching criteria, or instance eligibility, determines which instances are allowed to launch and run in the Capacity Reservation. A Capacity Reservation can have one of the following matching criteria: + **Open** — The Capacity Reservation automatically matches all instances that have matching attributes (instance type, platform, and Availability Zone). New and existing instances that have matching attributes automatically run in the Capacity Reservation without any additional configuration. + **Targeted** — The Capacity Reservation accepts only instances that have matching attributes (instance type, platform, and Availability Zone), and that explicitly target the Capacity Reservation. The instance must specifically target the Capacity Reservation to launch or run in its reserved capacity. This allows you to explicitly control which instances are allowed to run in the reserved capacity and helps you avoid unintentional reserved capacity usage. When you request a future-dated Capacity Reservation, you can specify only targeted matching criteria. This ensures that the capacity delivered by the Capacity Reservation is incremental, or additional, to any running instances or reserved capacity that you have at the time of delivery. After the Capacity Reservation becomes active in your account, you can change the instance matching criteria to open if needed. However, keep in mind that any matching instances will automatically run in the Capacity Reservation, which could lead to unintentional capacity usage and prevent you from launching new instances for the full requested instance count. ## 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: + [Reserved Instances for Amazon EC2 overview](ec2-reserved-instances.md) + [Savings Plans User Guide](https://docs.aws.amazon.com/savingsplans/latest/userguide/) ## 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 values for `platform`: + 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 To ensure that an instance runs in a specific Capacity Reservation, the platform of the Capacity Reservation must match the platform of the AMI used to launch the instance. For Linux AMIs, it is important to check whether the AMI platform uses the general value **Linux/UNIX** or a more specific value like **SUSE Linux**. ------ #### [ Console ] **To check the AMI platform** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation pane, choose **AMIs**. 1. Select the AMI. 1. On the **Details** tab, note the value of **Platform details**. ------ #### [ AWS CLI ] **To check the AMI platform** Use the [describe-images](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html) command and check the value of `PlatformDetails`. ``` aws ec2 describe-images \ --image-ids ami-0abcdef1234567890 \ --query Images[*].PlatformDetails ``` The following is example output. ``` [ "Linux/UNIX" ] ``` ------ #### [ PowerShell ] **To check the AMI platform** Use the [Get-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Image.html) cmdlet and check the value of `PlatformDetails`. ``` Get-EC2Image ` -ImageId ami-0abcdef1234567890 | ` Select PlatformDetails ``` The following is example output. ``` PlatformDetails --------------- Linux/UNIX ``` ------ ## 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](capacity-reservation-sharing.md). + 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). + [Red Hat instances] Capacity Reservations can 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 32 vCPUs. For example, if you request a future-dated Capacity Reservation for `m5.xlarge` instances, you must request at least 8 instances (*8 \$1 m5.xlarge = 32 vCPUs*). + You can request future-dated Capacity Reservations for instance types in the following series only: C, G, I, M, R, and T. # Capacity Reservation pricing and billing Pricing and billing The topics in this section provide an overview of pricing and billing for Capacity Reservations. **Topics** + [ ## Pricing ](#capacity-reservations-pricing) + [ ## Billing ](#capacity-reservations-billing) + [ ## Billing discounts ](#capacity-reservations-discounts) + [ ## Viewing your bill ](#capacity-reservations-viewing-bill) ## Pricing Capacity Reservations are charged at the equivalent On-Demand rate whether you run instances in reserved capacity or not, including any applicable regional surcharge for Dedicated Instances. If you do not use the reservation, this shows up as unused reservation on your Amazon EC2 bill. When you run an instance that matches the attributes of a reservation, you just pay for the instance and nothing for the reservation. There are no upfront or additional charges. For example, if you create a Capacity Reservation for 20 `m4.large` Linux instances and run 15 `m4.large` Linux instances in the same Availability Zone, you will be charged for 15 active instances and for 5 unused instances in the reservation. Billing discounts for Savings Plans and Regional Reserved Instances apply to Capacity Reservations. For more information, see [Billing discounts](#capacity-reservations-discounts). For more information, see [Amazon EC2 Pricing](https://aws.amazon.com/ec2/pricing/). ## Billing Billing starts as soon as the Capacity Reservation is provisioned in your account, and it continues while the Capacity Reservation remains provisioned in your account. For future-dated Capacity Reservations, this means that billing starts only once the Capacity Reservation is provisioned in your account at the requested future date. Capacity Reservations are billed at per-second granularity. This means that you are charged for partial hours. For example, if a Capacity Reservation remains provisioned in your account for `24` hours and `15` minutes, you are billed for `24.25` reservation hours. The following example shows how a Capacity Reservation is billed. The Capacity Reservation is created for one `m4.large` Linux instance, which has an On-Demand rate of \$10.10 per usage hour. In this example, the Capacity Reservation is provisioned in the account for five hours. The Capacity Reservation is unused for the first hour, so it is billed for one unused hour at the `m4.large` instance type's standard On-Demand rate. In hours two through five, the Capacity Reservation is occupied by an `m4.large` instance. During this time, the Capacity Reservation accrues no charges, and the account is instead billed for the `m4.large` instance occupying it. In the sixth hour, the Capacity Reservation is canceled and the `m4.large` instance runs normally outside of the reserved capacity. For that hour, it is charged at the On-Demand rate of the `m4.large` instance type. ![\[Capacity Reservation billing example\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/cr-billing-example.png) ## Billing discounts Billing discounts for Savings Plans and Regional Reserved Instances apply to Capacity Reservations. AWS automatically applies these discounts to Capacity Reservations that have matching attributes. When a Capacity Reservation is used by an instance, the discount is applied to the instance. Discounts are preferentially applied to instance usage before covering unused Capacity Reservations. Billing discounts for zonal Reserved Instances do not apply to Capacity Reservations. For more information, see the following: + [Reserved Instances for Amazon EC2 overview](ec2-reserved-instances.md) + [Savings Plans User Guide](https://docs.aws.amazon.com/savingsplans/latest/userguide/) + [Billing and purchase options](https://aws.amazon.com/ec2/faqs/#capacityreservations) ## Viewing your bill You can review the charges and fees to your account on the AWS Billing and Cost Management console. + The **Dashboard** displays a spend summary for your account. + On the **Bills** page, under **Details**, expand the **Elastic Compute Cloud** section and the Region to get billing information about your Capacity Reservations. You can view the charges online, or you can download a CSV file. For more information, see [Capacity Reservation line items](https://docs.aws.amazon.com/cur/latest/userguide/monitor-ondemand-reservations.html#capacity-reservation-li). # Create a Capacity Reservation You can create a Capacity Reservation at any time to ensure that you have compute capacity available in a specific Availability Zone. A Capacity Reservation can start immediately, or it can start at a future date. The capacity becomes available for use only once the Capacity Reservation enters the `active` state. **Note** If you create a Capacity Reservation with `open` instance matching criteria, and you have running instances with matching attributes at the time the Capacity Reservation becomes active, those instances automatically run in the reserved capacity. To avoid this, use `targeted` instance matching criteria. For more information, see [Instance matching criteria](cr-concepts.md#cr-instance-eligibility). Your request to create a Capacity Reservation could fail if one of the following is true: + Amazon EC2 does not have sufficient capacity to fulfill the request. Either try again at a later time, try a different Availability Zone, or try a smaller request. If your application is flexible across instance types and sizes, try different instance attributes. + The requested quantity exceeds your On-Demand Instance limit for the selected instance family. Increase your On-Demand Instance limit for the instance family and try again. For more information, see [On-Demand Instance quotas](ec2-on-demand-instances.md#ec2-on-demand-instances-limits). **Topics** + [ ## Create a Capacity Reservation for immediate use ](#create-immediate-cr) + [ ## Create a future-dated Capacity Reservation ](#create-future-cr) ## Create a Capacity Reservation for immediate use You create a Capacity Reservation for immediate use. ------ #### [ Console ] **To create a Capacity Reservation** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. Choose **Capacity Reservations**, and then choose **Create Capacity Reservation**. 1. Configure the following settings in the **Instance details** section. 1. **Instance Type** — The instance type for which to reserve capacity. 1. **Platform** — The operating system for your instances. For more information, see [Supported platforms](ec2-capacity-reservations.md#capacity-reservations-platforms). 1. **Availability Zone** — The Availability Zone in which to reserve the capacity. 1. **Tenancy** — The type of tenancy to use for the reserved capacity. Choose Default to reserve capacity on shared hardware, or Dedicated to reserve capacity on hardware that is dedicated to your account. 1. (*Optional*) **Placement group ARN** — The ARN of the cluster placement group in which to create the Capacity Reservation. For more information, see [Use Capacity Reservations with cluster placement groups](cr-cpg.md). 1. **Total instance count** — The number of instances for which to reserve capacity. If you specify a quantity that exceeds your remaining On-Demand Instance quota for the selected instance type, the request fails. 1. Configure the following settings in the **Reservation details** section: 1. **Capacity Reservation starts** — Choose **Immediately**. 1. **Capacity Reservation ends** — Choose one of the following options: + **Manually** — Reserve the capacity until you explicitly cancel it. + **Specific time** — Cancel the capacity reservation automatically at the specified date and time. 1. **Instance eligibility** — Choose one of the following options: + **open** — (Default) The Capacity Reservation matches any instance that has matching attributes (instance type, platform, Availability Zone, and tenancy). If you launch an instance with matching attributes, it is placed into the reserved capacity automatically. + **targeted** — The Capacity Reservation only accepts instances that have matching attributes (instance type, platform, Availability Zone, and tenancy), and that explicitly target the reservation. 1. Choose **Create**. ------ #### [ AWS CLI ] **To create a Capacity Reservation** Use the [create-capacity-reservation](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-capacity-reservation.html) command. ``` aws ec2 create-capacity-reservation \ --availability-zone az_name \ --instance-type instance_type \ --instance-count number_of_instances \ --instance-platform operating_system \ --instance-match-criteria open|targeted ``` ------ #### [ PowerShell ] **To create a Capacity Reservation** Use the [Add-EC2CapacityReservation](https://docs.aws.amazon.com/powershell/latest/reference/items/Add-EC2CapacityReservation.html) cmdlet. ``` Add-EC2CapacityReservation ` -AvailabilityZone az_name ` -InstanceType instance_type ` -InstanceCount number_of_instances ` -InstancePlatform operating_system ` -InstanceMatchCriterion open|targeted ``` ------ ## Create a future-dated Capacity Reservation Request a future-dated Capacity Reservation if you need the reserved capacity to become available at a future date and time. After you request a future-dated Capacity Reservation, the request undergoes an assessment to determine whether it can be supported. For more information, see [Future-dated Capacity Reservation assessment](cr-concepts.md#cr-future-dated-assessment). **Considerations** + You can request future-dated Capacity Reservations for instance types in the following series: C, G, I, M, R, and T. + You can request future-dated Capacity Reservations for an instance count with a minimum of 32 vCPUs. For example, if you request a future-dated Capacity Reservation for `m5.xlarge` instances, you must request capacity for at least 8 instances (*8 \$1 m5.xlarge = 32 vCPUs*). + You can request a future-dated Capacity Reservation between 5 and 120 days in advance. However, we recommend that you request it at least 56 days (8 weeks) in advance to improve supportability. + The minimum commitment duration is 14 days. ------ #### [ Console ] **To create a Capacity Reservation** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. Choose **Capacity Reservations**, and then choose **Create Capacity Reservation**. 1. Configure the following settings in the **Instance details** section. 1. **Instance Type** — The instance type for which to reserve capacity. 1. **Platform** — The operating system for your instances. For more information, see [Supported platforms](ec2-capacity-reservations.md#capacity-reservations-platforms). 1. **Availability Zone** — The Availability Zone in which to reserve the capacity. 1. **Tenancy** — The type of tenancy to use for the reserved capacity. Choose Default to reserve capacity on shared hardware, or Dedicated to reserve capacity on hardware that is dedicated to your account. 1. **Total instance count** — The number of instances for which to reserve capacity. If you specify a quantity that exceeds your remaining On-Demand Instance quota for the selected instance type, the request fails. 1. Configure the following settings in the **Reservation details** section: 1. **Capacity Reservation starts** — Choose **At a specific time**. 1. **Start date** — Specify the date and time at which the Capacity Reservation must become available for use. For more information, see [Start date and time](cr-concepts.md#cr-start-date). 1. **Commitment duration** — Specify the minimum duration for which you commit keeping the Capacity Reservation after it has been delivered. For more information, see [Commitment duration](cr-concepts.md#cr-commitment-duration). 1. **Capacity Reservation ends** — Choose one of the following options: + **When I cancel it** — Reserve the capacity until you explicitly cancel it. + **Specific time** — Cancel the capacity reservation automatically at the specified date and time. 1. Choose **Create**. ------ #### [ AWS CLI ] **To create a Capacity Reservation** Use the [create-capacity-reservation](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-capacity-reservation.html) command. ``` aws ec2 create-capacity-reservation \ --availability-zone az_name \ --instance-type instance_type \ --instance-count number_of_instances \ --instance-platform operating_system \ --instance-match-criteria targeted \ --delivery-preference incremental \ --commitment-duration commitment_in_seconds \ --start-date YYYY-MMDDThh:mm:ss.sssZ ``` ------ #### [ PowerShell ] **To create a Capacity Reservation** Use the [Add-EC2CapacityReservation](https://docs.aws.amazon.com/powershell/latest/reference/items/Add-EC2CapacityReservation.html) cmdlet. ``` Add-EC2CapacityReservation ` -AvailabilityZone az_name ` -InstanceType instance_type ` -InstanceCount number_of_instances ` -InstancePlatform operating_system ` -InstanceMatchCriterion targeted ` -DeliveryPreference incremental ` -CommitmentDuration commitment_in_seconds ` -StartDate YYYY-MMDDThh:mm:ss.sssZ ``` ------ # View the state of a Capacity Reservation Amazon EC2 constantly monitors the state of your Capacity Reservations. Due to the [eventual consistency](https://docs.aws.amazon.com/ec2/latest/devguide/eventual-consistency.html) model followed by the Amazon EC2 API, after you create a Capacity Reservation, it can take up to 5 minutes for the state of the Capacity Reservation to reflect that it is `active`. During this time, the Capacity Reservation might remain in the `pending` state. However, it might already be available for use, in which case attempts to launch instances into the Capacity Reservation would succeed. ------ #### [ Console ] **To view your Capacity Reservations** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation pane, choose **Capacity Reservations**. 1. Select the Capacity Reservation. ------ #### [ AWS CLI ] **To describe your Capacity Reservations** Use the [describe-capacity-reservations](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-capacity-reservations.html) command. For example, the following command describes all Capacity Reservations. ``` aws ec2 describe-capacity-reservations ``` The following is example output. ``` { "CapacityReservations": [ { "CapacityReservationId": "cr-1234abcd56EXAMPLE", "EndDateType": "unlimited", "AvailabilityZone": "eu-west-1a", "InstanceMatchCriteria": "open", "Tags": [], "EphemeralStorage": false, "CreateDate": "2019-08-16T09:03:18.000Z", "AvailableInstanceCount": 1, "InstancePlatform": "Linux/UNIX", "TotalInstanceCount": 1, "State": "active", "Tenancy": "default", "EbsOptimized": true, "InstanceType": "a1.medium", "PlacementGroupArn": "arn:aws:ec2:us-east-1:123456789012:placement-group/MyPG" }, { "CapacityReservationId": "cr-abcdEXAMPLE9876ef", "EndDateType": "unlimited", "AvailabilityZone": "eu-west-1a", "InstanceMatchCriteria": "open", "Tags": [], "EphemeralStorage": false, "CreateDate": "2019-08-07T11:34:19.000Z", "AvailableInstanceCount": 3, "InstancePlatform": "Linux/UNIX", "TotalInstanceCount": 3, "State": "cancelled", "Tenancy": "default", "EbsOptimized": true, "InstanceType": "m5.large" } ] } ``` ------ #### [ PowerShell ] **To describe a Capacity Reservation** Use the [Get-EC2CapacityReservation](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2CapacityReservation.html) cmdlet. ``` Get-EC2CapacityReservation ` -CapacityReservationId cr-1234abcd56EXAMPLE ``` ------ ## Capacity Reservation states Capacity Reservations have the following possible states. | State | Description | | --- | --- | | active | The capacity is available for use. | | expired | The Capacity Reservation expired automatically at the date and time specified in your reservation request. The reserved capacity is no longer available for your use. | | cancelled | The Capacity Reservation was canceled. The reserved capacity is no longer available for your use. | | pending | The Capacity Reservation request was successful but the capacity provisioning is still pending. | | failed | The Capacity Reservation request has failed. A request can fail due to request parameters that are not valid, capacity constraints, or instance limit constraints. You can view a failed request for 60 minutes. | | scheduled | (Future-dated Capacity Reservations only) The future-dated Capacity Reservation request was approved and the Capacity Reservation is scheduled for delivery on the requested start date. | | assessing | (Future-dated Capacity Reservations only) Amazon EC2 is assessing your request for a future-dated Capacity Reservation. For more information, see [Future-dated Capacity Reservation assessment](cr-concepts.md#cr-future-dated-assessment). | | delayed | (Future-dated Capacity Reservations only) Amazon EC2 encountered a delay in provisioning the requested future-dated Capacity Reservation. Amazon EC2 is unable to deliver the requested capacity by the requested start date and time. | | unsupported | (Future-dated Capacity Reservations only) Amazon EC2 can't support the future-dated Capacity Reservation request due to capacity constraints. You can view unsupported requests for 30 days. The Capacity Reservation will not be delivered. | # Launch instances into an existing Capacity Reservation Launch instances into Capacity Reservation You can only launch an instance into a Capacity Reservation that: + Has matching attributes (instance type, platform, Availability Zone, and tenancy) + Has sufficient available capacity + Is in the `active` state When you launch an instance, you can specify whether to launch the instance into any `open` Capacity Reservation, into a specific Capacity Reservation, or into a group of Capacity Reservations. Alternatively, you can configure the instance to avoid running in a Capacity Reservation, even if you have an `open` Capacity Reservation that has matching attributes and available capacity. Launching an instance into a Capacity Reservation reduces its available capacity by the number of instances launched. For example, if you launch three instances, the available capacity of the Capacity Reservation is reduced by three. ------ #### [ Console ] **To launch instances into an existing Capacity Reservation** 1. Follow the procedure to [launch an instance](ec2-launch-instance-wizard.md), but don't launch the instance until you've completed the following steps to specify the settings for the placement group and Capacity Reservation. 1. Expand **Advanced details** and do the following: 1. For **Placement group**, select the cluster placement group in which to launch the instance. 1. For **Capacity Reservation**, choose one of the following options depending on the configuration of the Capacity Reservation: + **None** – Prevents the instances from launching into a Capacity Reservation. The instances run in On-Demand capacity. + **Open** – Launches the instances into any Capacity Reservation that has matching attributes and sufficient capacity for the number of instances you selected. If there is no matching Capacity Reservation with sufficient capacity, the instance uses On-Demand capacity. + **Specify Capacity Reservation** – Launches the instances into the selected Capacity Reservation. If the selected Capacity Reservation does not have sufficient capacity for the number of instances you selected, the instance launch fails. + **Specify Capacity Reservation resource group** – Launches the instances into any Capacity Reservation with matching attributes and available capacity in the selected Capacity Reservation group. If the selected group does not have a Capacity Reservation with matching attributes and available capacity, the instances launch into On-Demand capacity. + **Specify Capacity Reservation only** – Launches the instances into a Capacity Reservation. If a Capacity Reservation ID isn't specified, the instances launch into an open Capacity Reservation. If capacity isn't available, the instances fail to launch. + **Specify Capacity Reservation resource group only** – Launches the instances into a Capacity Reservation in a Capacity Reservation resource group. If a Capacity Reservation resource group ARN isn't specified, the instances launch into an open Capacity Reservation. If capacity isn't available, the instances fail to launch. 1. In the **Summary** panel, review your instance configuration, and then choose **Launch instance**. ------ #### [ AWS CLI ] **To launch an instance into an existing Capacity Reservation** Use the [run-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command and specify the `--capacity-reservation-specification` option. The following example launches an instance into any open Capacity Reservation with matching attributes and available capacity: ``` aws ec2 run-instances \ --image-id ami-0abcdef1234567890 \ --count 1 \ --instance-type t2.micro \ --key-name my-key-pair \ --subnet-id subnet-0abcdef1234567890 \ --capacity-reservation-specification CapacityReservationPreference=open ``` The following example launches an instance into a `targeted` Capacity Reservation: ``` aws ec2 run-instances \ --image-id ami-0abcdef1234567890 \ --count 1 \ --instance-type t2.micro \ --key-name my-key-pair \ --subnet-id subnet-0abcdef1234567890 \ --capacity-reservation-specification \ CapacityReservationTarget={CapacityReservationId=cr-1234abcd56EXAMPLE} ``` The following example launches an instance into the specified Capacity Reservation group: ``` aws ec2 run-instances \ --image-id ami-0abcdef1234567890 \ --count 1 \ --instance-type t2.micro \ --key-name my-key-pair \ --subnet-id subnet-0abcdef1234567890 \ --capacity-reservation-specification \ CapacityReservationTarget={CapacityReservationResourceGroupArn=arn:aws:resource-groups:us-west-2:123456789012:group/my-cr-group} ``` The following example launches an instance into a Capacity Reservation only. Because it does not specify a Capacity Reservation ID, the instance launches in any open Capacity Reservation with matching attributes and available capacity: ``` aws ec2 run-instances \ --image-id ami-0abcdef1234567890 \ --count 1 \ --instance-type t2.micro \ --key-name my-key-pair \ --subnet-id subnet-0abcdef1234567890 \ --capacity-reservation-specification \ CapacityReservationPreference=capacity-reservations-only ``` The following example launches an instance into a specific Capacity Reservation only. If capacity isn't available in the specified Capacity Reservation, the instance fails to launch. ``` aws ec2 run-instances \ --image-id ami-0abcdef1234567890 \ --count 1 \ --instance-type t2.micro \ --key-name my-key-pair \ --subnet-id subnet-0abcdef1234567890 \ --capacity-reservation-specification \ CapacityReservationPreference=capacity-reservations-only \ CapacityReservationTarget={CapacityReservationId=cr-1234abcd56EXAMPLE} ``` ------ #### [ PowerShell ] **To launch an instance into an existing Capacity Reservation** Use the [New-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) cmdlet. The following example launches an instance into any open Capacity Reservation with matching attributes and available capacity: ``` New-EC2Instance ` -ImageId ami-0abcdef1234567890 ` -InstanceType t2.micro ` -KeyName "my-key-pair" ` -SubnetId subnet-0abcdef1234567890 ` -CapacityReservationSpecification_CapacityReservationPreference "open" ``` The following example launches an instance into a `targeted` Capacity Reservation: ``` New-EC2Instance ` -ImageId ami-0abcdef1234567890 ` -InstanceType t2.micro ` -KeyName "my-key-pair" ` -SubnetId subnet-0abcdef1234567890 ` -CapacityReservationTarget_CapacityReservationId cr-1234abcd56EXAMPLE ``` The following example launches an instance into the specified Capacity Reservation group: ``` New-EC2Instance ` -ImageId ami-0abcdef1234567890 ` -InstanceType t2.micro ` -KeyName "my-key-pair" ` -SubnetId subnet-0abcdef1234567890 ` -CapacityReservationTarget_CapacityReservationResourceGroupArn ` "arn:aws:resource-groups:us-west-2:123456789012:group/my-cr-group" ``` The following example launches an instance into a Capacity Reservation only. Because it does not specify a Capacity Reservation ID, the instance launches in any open Capacity Reservation with matching attributes and available capacity: ``` New-EC2Instance ` -ImageId ami-0abcdef1234567890 ` -InstanceType t2.micro ` -KeyName "my-key-pair" ` -SubnetId subnet-0abcdef1234567890 ` -CapacityReservationSpecification_CapacityReservationPreference "capacity-reservations-only" ``` The following example launches an instance into a specific Capacity Reservation only. If capacity isn't available in the specified Capacity Reservation, the instance fails to launch. ``` New-EC2Instance ` -ImageId ami-0abcdef1234567890 ` -InstanceType t2.micro ` -KeyName "my-key-pair" ` -SubnetId subnet-0abcdef1234567890 ` -CapacityReservationSpecification_CapacityReservationPreference "capacity-reservations-only" ` -CapacityReservationTarget_CapacityReservationId cr-1234abcd56EXAMPLE ``` ------ # Modify an active Capacity Reservation Modify Capacity Reservation If you have an existing Capacity Reservation which isn't a good fit for the workload that needs the capacity, you can modify the instance quantity, instance eligibility (`open` or `targeted`), and end time (`At specific time` or `Manually`). If you specify a new instance quantity that exceeds your remaining On-Demand Instance limit for the selected instance type, the update fails. The allowed modifications depend on the state of the Capacity Reservation: + `assessing` or `scheduled` state — You can modify the tags only. + `pending` state — You can't modify the Capacity Reservation in any way. + `active` state but still within the commitment duration — You can't decrease the instance count below the committed instance count, or set an end date that is before the committed duration. All other modifications are allowed. + `active` state with no commitment duration or elapsed commitment duration — All modifications are allowed. + `expired`, `cancelled`, `unsupported`, or `failed` state — You can't modify the Capacity Reservation in any way. **Considerations** + You can't change the instance type, platform, Availability Zone, or tenancy after creation. If you need to modify any of these attributes, we recommend that you cancel the reservation, and then create a new one with the required attributes. + If you modify an existing Capacity Reservation by changing the instance eligibility from `targeted` to `open`, any running instances that match the attributes of the Capacity Reservation, have the `CapacityReservationPreference` parameter set to `open`, and are not yet running in a Capacity Reservation, will automatically use the modified Capacity Reservation. + To change the instance eligibility, the Capacity Reservation must be completely idle (zero usage) because Amazon EC2 can't modify instance eligibility when instances are running inside the reservation. ------ #### [ Console ] **To modify a Capacity Reservation** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. Choose **Capacity Reservations**, select the Capacity Reservation to modify, and then choose **Edit**. 1. Modify the **Total capacity**, **Capacity Reservation ends**, or **Instance eligibility** options as needed, and choose **Save**. ------ #### [ AWS CLI ] **To modify a Capacity Reservation** Use the [modify-capacity-reservation](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-capacity-reservation.html) command. The following example modifies the specified Capacity Reservation to reserve capacity for eight instances. ``` aws ec2 modify-capacity-reservation \ --capacity-reservation-id cr-1234567890abcdef0 \ --instance-count 8 ``` ------ #### [ PowerShell ] **To modify a Capacity Reservation** Use the [Edit-EC2CapacityReservation](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2CapacityReservation.html) cmdlet. The following example modifies the specified Capacity Reservation to reserve capacity for eight instances. ``` Edit-EC2CapacityReservation ` -CapacityReservationId cr-1234567890abcdef0 ` -InstanceCount 8 ``` ------ # Modify the Capacity Reservation settings of your instance Modify instance Capacity Reservation settings You can modify the following Capacity Reservation settings for a stopped instance at any time: + Start in any Capacity Reservation that has matching attributes (instance type, platform, Availability Zone, and tenancy) and available capacity. + Start the instance in a specific Capacity Reservation. + Start in any Capacity Reservation that has matching attributes and available capacity in a Capacity Reservation group + Prevent the instance from starting in a Capacity Reservation. ------ #### [ Console ] **To modify instance Capacity Reservation settings** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. Choose **Instances** and select the instance to modify. Stop the instance if it is not already stopped. 1. Choose **Actions**, **Instance settings**, **Modify Capacity Reservation Settings**. 1. For **Capacity Reservation**, choose one of the following options: + **Open** – Launches the instances into any Capacity Reservation that has matching attributes and sufficient capacity for the number of instances you selected. If there is no matching Capacity Reservation with sufficient capacity, the instance uses On-Demand capacity. + **None** – Prevents the instances from launching into a Capacity Reservation. The instances run in On-Demand capacity. + **Specify Capacity Reservation** – Launches the instances into the selected Capacity Reservation. If the selected Capacity Reservation does not have sufficient capacity for the number of instances you selected, the instance launch fails. + **Specify Capacity Reservation group** – Launches the instances into any Capacity Reservation with matching attributes and available capacity in the selected Capacity Reservation group. If the selected group does not have a Capacity Reservation with matching attributes and available capacity, the instances launch into On-Demand capacity. + **Specify Capacity Reservation only** – Launches the instances into a Capacity Reservation. If a Capacity Reservation ID isn't specified, the instances launch into an open Capacity Reservation. If capacity isn't available, the instances fail to launch. + **Specify Capacity Reservation resource group only** – Launches the instances into a Capacity Reservation in a Capacity Reservation resource group. If a Capacity Reservation resource group ARN isn't specified, the instances launch into an open Capacity Reservation. If capacity isn't available, the instances fail to launch. ------ #### [ AWS CLI ] **To modify instance Capacity Reservation settings** Use the [modify-instance-capacity-reservation-attributes](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-capacity-reservation-attributes.html) command. The following example changes the Capacity Reservation preference to `none`. ``` aws ec2 modify-instance-capacity-reservation-attributes \ --instance-id i-1234567890abcdef0 \ --capacity-reservation-specification CapacityReservationPreference=none ``` The following example the target to a specific Capacity Reservation. ``` aws ec2 modify-instance-capacity-reservation-attributes \ --instance-id i-1234567890abcdef0 \ --capacity-reservation-specification \ CapacityReservationTarget={CapacityReservationId=cr-1234567890abcdef0} ``` The following example changes the target to a specific Capacity Reservation group. ``` aws ec2 modify-instance-capacity-reservation-attributes \ --instance-id i-1234567890abcdef0 \ --capacity-reservation-specification \ CapacityReservationTarget={CapacityReservationResourceGroupArn=arn:aws:resource-groups:us-west-2:123456789012:group/my-cr-group} ``` The following example changes the Capacity Reservation preference to `capacity-reservation-only`. Because it doesn't specify a Capacity Reservation, instances launch into any open Capacity Reservation with matching attributes and available capacity. ``` aws ec2 modify-instance-capacity-reservation-attributes \ --instance-id i-1234567890abcdef0 \ --capacity-reservation-specification CapacityReservationPreference=capacity-reservation-only ``` The following example changes the Capacity Reservation preference to `capacity-reservation-only` and changes the target to a specific Capacity Reservation. If capacity isn't available in the specified Capacity Reservation, the instances fail to launch. ``` aws ec2 modify-instance-capacity-reservation-attributes \ --instance-id i-1234567890abcdef0 \ --capacity-reservation-specification \ CapacityReservationPreference=capacity-reservation-only \ CapacityReservationTarget={CapacityReservationId=cr-1234567890abcdef0} ``` ------ #### [ PowerShell ] **To modify instance Capacity Reservation settings** Use the [Edit-EC2InstanceCapacityReservationAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceCapacityReservationAttribute.html) cmdlet. The following example changes the Capacity Reservation preference to `none`. ``` Edit-EC2InstanceCapacityReservationAttribute ` -InstanceId i-1234567890abcdef0 ` -CapacityReservationSpecification_CapacityReservationPreference "none" ``` The following example the target to a specific Capacity Reservation. ``` Edit-EC2InstanceCapacityReservationAttribute ` -InstanceId i-1234567890abcdef0 ` -CapacityReservationTarget_CapacityReservationId cr-1234567890abcdef0 ``` The following example changes the target to a specific Capacity Reservation group. ``` Edit-EC2InstanceCapacityReservationAttribute ` -InstanceId i-1234567890abcdef0 ` -CapacityReservationTarget_CapacityReservationResourceGroupArn ` "arn:aws:resource-groups:us-west-2:123456789012:group/my-cr-group" ``` The following example changes the Capacity Reservation preference to `capacity-reservation-only`. Because it doesn't specify a Capacity Reservation, instances launch into any open Capacity Reservation with matching attributes and available capacity. ``` Edit-EC2InstanceCapacityReservationAttribute ` -InstanceId i-1234567890abcdef0 ` -CapacityReservationSpecification_CapacityReservationPreference "capacity-reservation-only" ``` The following example changes the Capacity Reservation preference to `capacity-reservation-only` and changes the target to a specific Capacity Reservation. If capacity isn't available in the specified Capacity Reservation, the instances fail to launch. ``` Edit-EC2InstanceCapacityReservationAttribute ` -InstanceId i-1234567890abcdef0 ` -CapacityReservationSpecification_CapacityReservationPreference "capacity-reservation-only" ` -CapacityReservationTarget_CapacityReservationId cr-1234567890abcdef0 ``` ------ # Move capacity between Capacity Reservations Move capacity You can move capacity from one Capacity Reservation to another to redistribute your reserved compute resources as needed. For example, if you need additional capacity in a reservation with growing usage, and you have capacity available in another reservation, then you can reallocate that capacity between the two reservations. ## Prerequisites for moving capacity As a prerequisite, the two Capacity Reservations must meet the following requirements: + Both reservations must be in the active state. + Both reservations must be owned by your AWS account. You cannot move capacity between reservations owned by different AWS accounts. + Both reservations must have the same: + Instance type + Platform + Availability Zone + Tenancy + Placement group + End time The destination Capacity Reservations instance eligibility (`open` or `targeted`), and tags, don't have to match the source reservation. The configuration of both reservations remains the same, except that the source reservation has reduced capacity and the destination reservation has increased capacity. When you specify the quantity of instances to be moved, by default, any available capacity is moved first, followed by any eligible running instances (the used capacity in your reservation). For example, if you move 4 instances from a reservation with 5 used instances and 3 available instances, then the 3 available instances and 1 used instance will be moved. **Note** When you move used capacity from your reservation by specifying a **Quantity to move** that's greater than the available capacity, only the instances that were launched with their **Capacity Reservation Specification** as `open` will be moved. ## Considerations The following considerations apply when moving capacity from one reservation to another: + The used capacity can only be moved between Capacity Reservations with `open` instance eligibility that are shared with the same set of accounts. + When you move used capacity, the eligible instances are randomly selected. You cannot specify which running instances are moved. If a sufficient number of eligible instances are not found to fulfill the move quantity, the move operation will fail. + If you move all of the capacity from the source reservation, the Capacity Reservation will be automatically canceled. + **Future-dated Capacity Reservations ** — You can't move capacity for a future-dated Capacity Reservation during the commitment period. **Note** Moving capacity from a Capacity Block isn't supported. ## Move capacity You can move capacity from a source Capacity Reservation to a destination Capacity Reservation. ------ #### [ Console ] **To move capacity** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the left navigation pane, choose **Capacity Reservations**. 1. Select an On-Demand Capacity Reservation ID that has capacity to move. 1. Under **Actions**, **Manage capacity**, choose **Move**. 1. On the **Move capacity** page, under **Destination Capacity Reservation**, select a reservation from the list. 1. Under **Quantity to move**, use the slider or type the number of instances to move from the source Capacity Reservation to the destination Capacity Reservation. 1. Review the summary, and when you're ready, choose **Move**. ------ #### [ AWS CLI ] **To move capacity** Use the [move-capacity-reservation-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/move-capacity-reservation-instances.html) command. The following example moves 10 instances from the specified source Capacity Reservation to the specified destination Capacity Reservation. ``` aws ec2 move-capacity-reservation-instances \ --source-capacity-reservation-id cr-1234567890abcdef0 \ --destination-capacity-reservation-id cr-021345abcdef56789 \ --instance-count 10 ``` ------ #### [ PowerShell ] **To move capacity** Use the [Move-EC2CapacityReservationInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Move-EC2CapacityReservationInstance.html) cmdlet. The following example moves 10 instances from the specified source Capacity Reservation to the specified destination Capacity Reservation. ``` Move-EC2CapacityReservationInstance ` -SourceCapacityReservationId cr-1234567890abcdef0 ` -DestinationCapacityReservationId cr-021345abcdef56789 ` -InstanceCount 10 ``` ------ # Split off capacity from an existing Capacity Reservation Split off capacity You can split off capacity from an existing Capacity Reservation to create a new reservation. By splitting capacity, you allocate a portion of the original reservation to a specific workload or share it with another AWS account. For example, to partially share a Capacity Reservation with another account, you can split off some of the capacity to create a smaller sized Capacity Reservation. The smaller sized Capacity Reservation can then be shared with the other accounts using [AWS Resource Access Manager](https://docs.aws.amazon.com/ram/latest/userguide/what-is.html). When you split capacity from an existing Capacity Reservation, a new Capacity Reservation is automatically created. The existing reservation will be unchanged, except for the reduced total capacity from the number of instances split off. Instances that are running in the existing Capacity Reservation are not affected. You can split the existing reservation into only one new Capacity Reservation. The new Capacity Reservation will have the same configuration as the existing Capacity Reservation except for tags. By default, the new Capacity Reservation doesn't have any tags. You can specify new tags during the split operation. The new Capacity Reservation can also be modified after it is created, if necessary. When you specify the quantity of instances to be split, by default, any available capacity is split first, followed by any eligible running instances (the used capacity in your reservation). For example: if you split 4 instances from a Capacity Reservation with 5 used instances and 3 available instances, then the 3 available instances and 1 used instance will be split into a new reservation. ## Prerequisites for splitting capacity As a prerequisite, your Capacity Reservation must meet the following requirements: + The source reservation must be in the active state. + The source reservation must be owned by your AWS account. **Note** When you split used capacity from your reservation by specifying a **Quantity to split** that's greater than the available capacity, only the instances that were launched with their **Capacity Reservation Specification** as `open` will be split. ## Considerations The following considerations apply when splitting off capacity from one reservation to a new one: + The used capacity can only be split for Capacity Reservations with “open” instance eligibility that are not shared with any account. + When you split the used capacity, the eligible instances are randomly selected. You cannot specify which running instances are split. If a sufficient number of eligible instances are not found to fulfill the split quantity, the split operation will fail. + The maximum quantity of instances to split from an existing reservation is the size of the reservation minus one. For example, if your reservation’s total capacity is 5 instances, you can split a maximum of 4 instances into a new reservation. + **Future-dated Capacity Reservations ** – You can't split capacity for a future-dated Capacity Reservation during the commitment period. + **Resource groups** – If the existing Capacity Reservation belongs to a resource group, the new Capacity Reservation will not be automatically added to the resource group. You can add the new Capacity Reservation to a resource group after it is created, if necessary. + **Sharing** – If the existing Capacity Reservation is shared with a consumer account, the new Capacity Reservation will not be automatically shared with the consumer account. You can share the new Capacity Reservation after it is created, if necessary. + **Cluster placement group** – If the existing Capacity Reservation is part of a cluster placement group, the new Capacity Reservation will be created in the same cluster placement group. **Note** Splitting capacity from a Capacity Block isn't supported. ## Control access for splitting Capacity Reservations using tags You can use tags to control access to Amazon EC2 resources, including splitting capacity from an existing Capacity Reservation to create a new Capacity Reservation. For more information, see [ Controlling access to AWS resources using tags](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_tags.html) in the *IAM User Guide*. To control access for splitting a Capacity Reservation using tags, make sure that you specify both resource and request tags in the policy statement because IAM policies are evaluated against both the source Capacity Reservation and the newly created Capacity Reservation. The following example policy includes the `ec2:ResourceTag` condition key with the tag `Owner=ExampleDepartment1` for the source Capacity Reservation and the `ec2:RequestTag` condition key with the tag `stack=production` for the newly created Capacity Reservation. ``` { "Statement": [ { "Sid": "AllowSourceCapacityReservation", "Effect": "Allow", "Action": "ec2:CreateCapacityReservationBySplitting", "Resource": "arn:aws:ec2:us-east-1:111122223333:capacity-reservation/cr-1234567890abcdef0", "Condition": { "StringEquals": { "ec2:ResourceTag/Owner": "ExampleDepartment1" } } }, { "Sid": "AllowNewlyCreatedCapacityReservation", "Effect": "Allow", "Action": ["ec2:CreateCapacityReservationBySplitting", "ec2:CreateTags"], "Resource": "arn:aws:ec2:us-east-1:111122223333:capacity-reservation/*", "Condition": { "StringEquals": { "aws:RequestTag/stack": "production" } } } ] } ``` ## Split off capacity You can split off capacity from an existing Capacity Reservation to create a new Capacity Reservation. ------ #### [ Console ] **To split off capacity** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the left navigation pane, choose **Capacity Reservations**. 1. Select an On-Demand Capacity Reservation ID that has capacity to split. 1. Under **Actions**, **Manage capacity**, choose **Split**. 1. On the **Split Capacity Reservation** page, under **Quantity to split**, use the slider or type the number of instances to split from the current reservation. 1. (Optional) Add tags for the new Capacity Reservation. 1. Review the summary, and when you're ready, choose **Split**. ------ #### [ AWS CLI ] **To split off capacity** Use the `create-capacity-reservation-by-splitting` command. The following example creates a new Capacity Reservation by splitting off 10 instances from the specified Capacity Reservation. ``` aws ec2 create-capacity-reservation-by-splitting \ --source-capacity-reservation-id cr-1234567890abdef0 \ --instance-count 10 ``` ------ #### [ PowerShell ] **To split off capacity** Use the [New-EC2CapacityReservationBySplitting](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2CapacityReservationBySplitting.html) cmdlet. The following example creates a new Capacity Reservation by splitting off 10 instances from the specified Capacity Reservation. ``` New-EC2CapacityReservationBySplitting ` -SourceCapacityReservationId cr-1234567890abdef0 ` -InstanceCount 10 ``` ------ # Cancel a Capacity Reservation You can cancel a Capacity Reservation that is in one of the following states: + `assessing` + `active` and there is no commitment duration or the commitment duration has elapsed. You can't cancel a future-dated Capacity Reservation during the commitment duration. **Note** You can't modify or cancel a Capacity Block. For more information, see [Capacity Blocks for ML](ec2-capacity-blocks.md). If a future-dated Capacity Reservation enters the `delayed` state, the commitment duration is waived, and you can cancel it as soon as it enters the `active` state. When you cancel a Capacity Reservation, the capacity is released immediately, and it is no longer reserved for your use. You can cancel empty Capacity Reservations and Capacity Reservations that have running instances. If you cancel a Capacity Reservation that has running instances, the instances continue to run normally outside of the capacity reservation at standard On-Demand Instance rates or at a discounted rate if you have a matching Savings Plans or Regional Reserved Instance. After you cancel a Capacity Reservation, instances that target it can no longer launch. Modify these instances so that they either target a different Capacity Reservation, launch into any open Capacity Reservation with matching attributes and sufficient capacity, or avoid launching into a Capacity Reservation. For more information, see [Modify the Capacity Reservation settings of your instance](capacity-reservations-modify-instance.md). ------ #### [ Console ] **To cancel a Capacity Reservation** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. Choose **Capacity Reservations** and select the Capacity Reservation to cancel. 1. Choose **Cancel reservation**, **Cancel reservation**. ------ #### [ AWS CLI ] **To cancel a Capacity Reservation** Use the [cancel-capacity-reservation](https://docs.aws.amazon.com/cli/latest/reference/ec2/cancel-capacity-reservation.html) command. ``` aws ec2 cancel-capacity-reservation \ --capacity-reservation-id cr-1234567890abcdef0 ``` ------ #### [ PowerShell ] **To cancel a Capacity Reservation** Use the [Remove-EC2CapacityReservation](https://docs.aws.amazon.com/powershell/latest/reference/items/Remove-EC2CapacityReservation.html) cmdlet. ``` Remove-EC2CapacityReservation ` -CapacityReservationId cr-1234567890abcdef0 ``` ------ # Use Capacity Reservations with cluster placement groups You can create Capacity Reservations in a cluster placement group to reserve Amazon EC2 compute capacity for your workloads. Cluster placement groups offer the benefit of low network latency and high network throughput. Creating a Capacity Reservation in a cluster placement group ensures that you have access to compute capacity in your cluster placement groups when you need it, for as long as you need it. This is ideal for reserving capacity for high-performance (HPC) workloads that require compute scaling. It allows you to scale your cluster down while ensuring that the capacity remains available for your use so that you can scale back up when needed. After you create a Capacity Reservation in a cluster placement group, you can share it with other AWS accounts. For more information, see [Sharing Capacity Reservations in cluster placement groups](#cpg-cr-sharing). **Topics** + [ ## Limitations ](#cr-cpg-limitations) + [ ## Work with Capacity Reservations in cluster placement groups ](#work-with-crs-cpgs) + [ ## Sharing Capacity Reservations in cluster placement groups ](#cpg-cr-sharing) ## Limitations Keep the following in mind when creating Capacity Reservations in cluster placement groups: + If an existing Capacity Reservation is not in a placement group, you can't modify the Capacity Reservation to reserve capacity in a placement group. To reserve capacity in a placement group, you must create the Capacity Reservation in the placement group. + After you create a Capacity Reservation in a placement group, you can't modify it to reserve capacity outside of the placement group. + You can increase your reserved capacity in a placement group by modifying an existing Capacity Reservation in the placement group, or by creating additional Capacity Reservations in the placement group. However, you increase your chances of getting an insufficient capacity error. + You can share Capacity Reservations only from the cluster placement group that you own. You cannot share Capacity Reservations from a cluster placement group that you do not own. + You can't delete a cluster placement group that has `active` Capacity Reservations. You must cancel all Capacity Reservations in the cluster placement group before you can delete it. ## Work with Capacity Reservations in cluster placement groups To start using Capacity Reservations with cluster placement groups, perform the following steps. **Note** If you want to create a Capacity Reservation in an existing cluster placement group, skip Step 1. Then for Steps 2 and 3, specify the ARN of the existing cluster placement group. **Topics** + [ ### Step 1: (*Conditional*) Create a cluster placement group for use with a Capacity Reservation ](#create-cpg) + [ ### Step 2: Create a Capacity Reservation in a cluster placement group ](#create-cr-in-cpg) + [ ### Step 3: Launch instances into Capacity Reservations in a cluster placement group ](#launch-instance-into-cpg) ### Step 1: (*Conditional*) Create a cluster placement group for use with a Capacity Reservation Perform this step only if you need to create a new cluster placement group. To use an existing cluster placement group, skip this step and then for Steps 2 and 3, use the ARN of that cluster placement group. ------ #### [ Console ] **To create a cluster placement group** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation pane, choose **Placement Groups**, and then choose **Create placement group**. 1. For **Name**, specify a descriptive name for the placement group. 1. For **Placement strategy**, choose **Cluster**. 1. Choose **Create group**. 1. In the **Placement groups** table, in the **Group ARN** column, make a note of the ARN of the cluster placement group that you created. You'll need it for the next step. ------ #### [ AWS CLI ] **To create a cluster placement group** Use the [create-placement-group](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-placement-group.html) command. ``` aws ec2 create-placement-group \ --group-name MyPG \ --strategy cluster ``` Make a note of the placement group ARN returned in the output, because you'll need it for the next step. ------ #### [ PowerShell ] **To create a cluster placement group** Use the [New-EC2PlacementGroup](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2PlacementGroup.html) cmdlet. ``` New-EC2PlacementGroup ` -GroupName my-placement-group ` -Strategy "cluster" ``` Make a note of the placement group ARN returned in the output, because you'll need it for the next step. ------ ### Step 2: Create a Capacity Reservation in a cluster placement group You create a Capacity Reservation in a cluster placement group in the same way that you create any Capacity Reservation. However, you must also specify the ARN of the cluster placement group in which to create the Capacity Reservation. **Considerations** + The specified cluster placement group must be in the `available` state. If the cluster placement group is in the `pending`, `deleting`, or `deleted` state, the request fails. + The Capacity Reservation and the cluster placement group must be in the same Availability Zone. If the request to create the Capacity Reservation specifies an Availability Zone that is different from that of the cluster placement group, the request fails. + You can create Capacity Reservations only for instance types that are supported by cluster placement groups. If you specify an unsupported instance type, the request fails. + If you create an `open` Capacity Reservation in a cluster placement group and there are existing running instances that have matching attributes (placement group ARN, instance type, Availability Zone, platform, and tenancy), those instances automatically run in the Capacity Reservation. + Your request to create a Capacity Reservation could fail if one of the following is true: + Amazon EC2 does not have sufficient capacity to fulfill the request. Either try again at a later time, try a different Availability Zone, or try a smaller capacity. If your workload is flexible across instance types and sizes, try different instance attributes. + The requested quantity exceeds your On-Demand Instance limit for the selected instance family. Increase your On-Demand Instance limit for the instance family and try again. For more information, see [On-Demand Instance quotas](ec2-on-demand-instances.md#ec2-on-demand-instances-limits). ------ #### [ Console ] **To create a Capacity Reservation** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. Choose **Capacity Reservations**, and then choose **Create Capacity Reservation**. 1. On the **Create a Capacity Reservation** page, specify the instance type, platform, Availability Zone, Tenancy, quantity, and end date as needed. 1. For **Placement group**, select the ARN of the cluster placement group in which to create the Capacity Reservation. 1. Choose **Create**. For more information, see [Create a Capacity Reservation](capacity-reservations-create.md). ------ #### [ AWS CLI ] **To create a Capacity Reservation** Use the [create-capacity-reservation](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-capacity-reservation.html) command. For `--placement-group-arn`, specify the ARN of the cluster placement group in which to create the Capacity Reservation. ``` aws ec2 create-capacity-reservation \ --instance-type instance_type \ --instance-platform platform \ --availability-zone-id az_id \ --instance-count quantity \ --placement-group-arn "placement_group_arn" ``` ------ #### [ PowerShell ] **To create a Capacity Reservation** Use the [Add-EC2CapacityReservation](https://docs.aws.amazon.com/powershell/latest/reference/items/Add-EC2CapacityReservation.html) cmdlet. For `-PlacementGroupArn`, specify the ARN of the cluster placement group in which to create the Capacity Reservation. ``` Add-EC2CapacityReservation ` -InstanceType instance_type ` -InstancePlatform platform ` -AvailabilityZoneId az_id ` -InstanceCount quantity ` -PlacementGroupArn "placement_group_arn" ``` ------ ### Step 3: Launch instances into Capacity Reservations in a cluster placement group You can launch an instance into a Capacity Reservation that is in a cluster placement group with one of the following options: + *Specifying the ARN of the cluster placement group in which to launch the instance* – When you provide the ARN of a cluster placement group, Amazon EC2 launches the instance into that cluster placement group. You can use one of the following methods: + *Specifying `open`* – You do not have to specify the Capacity Reservation in the instance launch request. If the instance has attributes (placement group ARN, instance type, Availability Zone, platform, and tenancy) that match a Capacity Reservation in the specified placement group, the instance automatically runs in the Capacity Reservation. + *Specifying a Capacity Reservation* – If the Capacity Reservation accepts only targeted instance launches, you must specify the target Capacity Reservation in addition to the cluster placement group in the request. + *Specifying a Capacity Reservation group* – For more information, see [ Using Capacity Reservation in cluster placement groups with a Capacity Reservation group](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cpg-odcr-crg.html). + *Specifying only a Capacity Reservation group* – For more information, see [Using Capacity Reservation in cluster placement groups with a Capacity Reservation group](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cpg-odcr-crg.html). + *Specifying only a Capacity Reservation* – You can launch instances into a Capacity Reservation in a cluster placement group. **Note** When you launch instances by specifying only a Capacity Reservation or only a Capacity Reservation group, the instances are launched into the Capacity Reservations that are created in the cluster placement group, but the instances are not directly attached to the cluster placement group. ------ #### [ Console ] **To launch instances into an existing Capacity Reservation** 1. Follow the procedure to [launch an instance](ec2-launch-instance-wizard.md), but don't launch the instance until you've completed the following steps to specify the settings for the placement group and Capacity Reservation. 1. Expand **Advanced details** and do the following: 1. For **Placement group**, select the cluster placement group in which to launch the instance. 1. For **Capacity Reservation**, choose one of the following options depending on the configuration of the Capacity Reservation: + **Open** – To launch the instances into any `open` Capacity Reservation in the cluster placement group that has matching attributes and sufficient capacity. + **Target by ID** – To launch the instances into a Capacity Reservation that accepts only targeted instance launches. + **Target by group** – To launch the instances into any Capacity Reservation with matching attributes and available capacity in the selected Capacity Reservation group. 1. In the **Summary** panel, review your instance configuration, and then choose **Launch instance**. For more information, see [Launch an EC2 instance using the launch instance wizard in the console](ec2-launch-instance-wizard.md). ------ #### [ AWS CLI ] **To launch instances into an existing Capacity Reservation** Use the [run-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command. If you need to target a specific Capacity Reservation or a Capacity Reservation group, specify the `--capacity-reservation-specification` parameter. For `--placement`, specify the `GroupName` parameter and then specify the name of the placement group that you created in the previous steps. ``` aws ec2 run-instances \ --image-id ami-0abcdef1234567890 \ --count quantity \ --instance-type instance_type \ --key-name key_pair_name \ --subnet-id subnet-0abcdef1234567890 \ --capacity-reservation-specification CapacityReservationTarget={CapacityReservationId=capacity_reservation_id} \ --placement "GroupName=cluster_placement_group_name" ``` ------ #### [ PowerShell ] **To launch instances into an existing Capacity Reservation** Use the [New-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) cmdlet. For `-Placement`, specify the `GroupName` parameter and then specify the name of the placement group that you created in the previous steps. ``` New-EC2Instance ` -ImageId ami-0abcdef1234567890 ` -InstanceType instance_type ` -KeyName key_pair_name ` -SubnetId subnet-0abcdef1234567890 ` -CapacityReservationTarget_CapacityReservationId capacity_reservation_id ` -Placement_GroupName cluster_placement_group_name ``` ------ ## Sharing Capacity Reservations in cluster placement groups You can share Capacity Reservations in cluster placement groups by either sharing only the Capacity Reservations, or by sharing both the Capacity Reservations and the cluster placement group in which they were created. By sharing only the Capacity Reservation, you give consumer accounts access to that Capacity Reservation only. Consumer accounts have no visibility or access to the cluster placement group in which the Capacity Reservation is created. This gives you fine-grained control over consumer account access. Consumer accounts can't view any information about the cluster placement group, including its ARN. When you share the cluster placement group and the Capacity Reservation, the cluster placement group is visible and accessible to consumer accounts. They can launch instances and create their own Capacity Reservations in it. For more information, see the following resources. + [Launch instances into Capacity Reservations in a cluster placement group](#launch-instance-into-cpg) + [Shared Capacity Reservations](capacity-reservation-sharing.md) + [Shared placement groups](share-placement-group.md) # Capacity Reservation groups You can use AWS Resource Groups to create logical collections of Capacity Reservations, called *resource groups*. A resource group is a logical grouping of AWS resources that are all in the same AWS Region. For more information about resource groups, see [What are resource groups?](https://docs.aws.amazon.com/ARG/latest/userguide/) in the *AWS Resource Groups User Guide*. You can include Capacity Reservations that you own in your account, and Capacity Reservations that are shared with you by other AWS accounts in a single resource group. You can also include Capacity Reservations that have different attributes (instance type, platform, Availability Zone, and tenancy) in a single resource group. When you create resource groups for Capacity Reservations, you can target instances to a group of Capacity Reservations instead of an individual Capacity Reservation. Instances that target a group of Capacity Reservations match with any Capacity Reservation in the group that has matching attributes (instance type, platform, Availability Zone, and tenancy) and available capacity. If the group does not have a Capacity Reservation with matching attributes and available capacity, the instances run using On-Demand capacity. If a matching Capacity Reservation is added to the targeted group at a later stage, the instance is automatically matched with and moved into its reserved capacity. To prevent unintended use of Capacity Reservations in a group, configure the Capacity Reservations in the group to accept only instances that explicitly target the capacity reservation. To do this, set **Instance eligibility** to **Only instances that specify this reservation** when creating the Capacity Reservation using the Amazon EC2 console. When using the AWS CLI, specify `--instance-match-criteria targeted` when creating the Capacity Reservation. Doing this ensures that only instances that explicitly target the group, or a Capacity Reservation in the group, can run in the group. If a Capacity Reservation in a group is canceled or expires while it has running instances, the instances are automatically moved to another Capacity Reservation in the group that has matching attributes and available capacity. If there are no remaining Capacity Reservations in the group that have matching attributes and available capacity, the instances run in On-Demand capacity. If a matching Capacity Reservation is added to the targeted group at a later stage, the instance is automatically moved into its reserved capacity. **Topics** + [Create a group](create-group.md) + [Add Capacity Reservation to group](add-to-group.md) + [Remove Capacity Reservation from group](remove-from-group.md) + [Delete group](delete-group.md) + [Using Capacity Reservation in cluster placement groups with a Capacity Reservation group](using-cpg-odcr-crg.md) # Create a Capacity Reservation group Create a group You can use the following examples to create a resource group for Capacity Reservations with the following request parameters. + `AWS::EC2::CapacityReservationPool` – Ensures that the resource group can be targeted for instance launches. + `AWS::ResourceGroups::Generic` with `allowed-resource-types` set to `AWS::EC2::CapacityReservation` – Ensures that the resource group accepts Capacity Reservations only. After you create a group, you can [add Capacity Reservations](add-to-group.md) to the group. ------ #### [ AWS CLI ] **To create a group for Capacity Reservations** Use the [create-group](https://docs.aws.amazon.com/cli/latest/reference/resource-groups/create-group.html) AWS CLI command. ``` aws resource-groups create-group \ --name MyCRGroup \ --configuration \ '{"Type": "AWS::EC2::CapacityReservationPool"}' \ '{"Type": "AWS::ResourceGroups::Generic", "Parameters": [{"Name": "allowed-resource-types", "Values": ["AWS::EC2::CapacityReservation"]}]}' ``` ------ #### [ PowerShell ] **To create a group for Capacity Reservations** Use the [New-RGGroup](https://docs.aws.amazon.com/powershell/latest/reference/items/New-RGGroup.html) cmdlet. ``` New-RGGroup ` -Name MyCRGroup ` -Configuration ` @{"Type"="AWS::EC2::CapacityReserationPool"} ` @{"Type"="AWS::ResourceGroups::Generic"; "Parameters"=@{"allowed-resource-types"=@{"Values"="AWS::EC2::CapacityReservations"}}} ``` ------ # Add a Capacity Reservation to a group Add Capacity Reservation to group If you add a Capacity Reservation that is shared with you to a group, and that Capacity Reservation is unshared, it is automatically removed from the group. ------ #### [ AWS CLI ] **To add a Capacity Reservation to a group** Use the [group-resources](https://docs.aws.amazon.com/cli/latest/reference/resource-groups/group-resources.html) command. The following example adds two Capacity Reservations to the specified group. ``` aws resource-groups group-resources \ --group MyCRGroup \ --resource-arns \ arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-1234567890abcdef1 \ arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-54321abcdef567890 ``` ------ #### [ PowerShell ] **To add a Capacity Reservation to a group** Use the [Add-RGResource](https://docs.aws.amazon.com/powershell/latest/reference/items/Add-RGResource.html) cmdlet. The following example adds two Capacity Reservations to the specified group. ``` Add-RGResource ` -Group MyCRGroup ` -ResourceArn ` "arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-1234567890abcdef1", ` "arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-54321abcdef567890" ``` ------ # Remove a Capacity Reservation from a group Remove Capacity Reservation from group You can use the following examples to remove a Capacity Reservation from a group. ------ #### [ AWS CLI ] **To remove a Capacity Reservation from a group** Use the [ungroup-resources](https://docs.aws.amazon.com/cli/latest/reference/resource-groups/ungroup-resources.html) command. The following example removes two Capacity Reservations from the specified group. ``` aws resource-groups ungroup-resources \ --group MyCRGroup \ --resource-arns \ arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-0e154d26a16094dd \ arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-54321abcdef567890 ``` ------ #### [ PowerShell ] **To remove a Capacity Reservation from a group** Use the [Remove-RGResource](https://docs.aws.amazon.com/powershell/latest/reference/items/Remove-RGResource.html) cmdlet. The following example removes two Capacity Reservations from the specified group. ``` Remove-RGResource ` -Group MyCRGroup ` -ResourceArn ` "arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-0e154d26a16094dd", ` "arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-54321abcdef567890" ``` ------ # Delete a Capacity Reservation group Delete group You can use the following examples to delete a Capacity Reservation group. ------ #### [ AWS CLI ] **To delete a group** Use the [delete-group](https://docs.aws.amazon.com/cli/latest/reference/resource-groups/delete-group.html) command. ``` aws resource-groups delete-group --group MyCRGroup ``` ------ #### [ PowerShell ] **To delete a group** Use the [Remove-RGGroup](https://docs.aws.amazon.com/powershell/latest/reference/items/Remove-RGGroup.html) cmdlet. ``` Remove-RGGroup -GroupName MyCRGroup ``` ------ # Using Capacity Reservation in cluster placement groups with a Capacity Reservation group Using Capacity Reservation in cluster placement groups with a Capacity Reservation group Amazon EC2 provides different launch methods for you to use Capacity Reservations in a cluster placement group with a Capacity Reservation group. You can choose one of the following methods to target a Capacity Reservation group based on your workload requirements: + *Specifying the ARN of the cluster placement group and Capacity Reservation group* – This will use any available Capacity Reservation with matching attributes and available capacity in the selected Capacity Reservation group. If the selected group does not have a Capacity Reservation with matching attributes and available capacity, the instances launch into On-Demand capacity. **Note** When you launch instances using this method, the instances are placed in the specified cluster placement group. + *Specifying only a Capacity Reservation group* – This will use all available capacity within the Capacity Reservation group by specifying only the Capacity Reservation group. While launching instances, capacity is used in the following order: + Capacity Reservations not associated with any cluster placement group. + Capacity Reservation in any cluster placement group within the Capacity Reservation group. + If the group does not have a Capacity Reservation with matching attributes and available capacity, the instances run using On-Demand capacity and they are not placed in any cluster placement group. **Note** When you launch instances by specifying only a Capacity Reservation group, the instances are launched into the Capacity Reservations that are created in the cluster placement group, but the instances are not directly attached to the cluster placement group. # Capacity Reservations in Local Zones A Local Zone is an extension of an AWS Region that is geographically close to your users. Resources created in a Local Zone can serve local users with very low-latency communications. For more information, see [AWS Local Zones](https://aws.amazon.com/about-aws/global-infrastructure/localzones/). You can extend a VPC from its parent AWS Region into a Local Zone by creating a new subnet in that Local Zone. When you create a subnet in a Local Zone, your VPC is extended to that Local Zone. The subnet in the Local Zone operates the same as the other subnets in your VPC. By using Local Zones, you can place Capacity Reservations in multiple locations that are closer to your users. You create and use Capacity Reservations in Local Zones in the same way that you create and use Capacity Reservations in regular Availability Zones. The same features and instance matching behavior apply. For more information about the pricing models that are supported in Local Zones, see [AWS Local Zones FAQs](https://aws.amazon.com/about-aws/global-infrastructure/localzones/faqs/). **Considerations** You can't use Capacity Reservation groups in a Local Zone. **To use a Capacity Reservation in a Local Zone** 1. Enable the Local Zone for use in your AWS account. For more information, see [Getting started with AWS Local Zones](https://docs.aws.amazon.com/local-zones/latest/ug/getting-started.html) in the *AWS Local Zones User Guide*. 1. Create a Capacity Reservation in the Local Zone. For **Availability Zone**, choose the Local Zone. The Local Zone is represented by an AWS Region code followed by an identifier that indicates the location, for example `us-west-2-lax-1a`. For more information, see [Create a Capacity Reservation](capacity-reservations-create.md). 1. Create a subnet in the Local Zone. For **Availability Zone**, choose the Local Zone. For more information, see [Create a subnet in your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/create-subnets.html) in the *Amazon VPC User Guide*. 1. Launch an instance. For **Subnet**, choose the subnet in the Local Zone (for example `subnet-123abc | us-west-2-lax-1a`), and for **Capacity Reservation**, choose the specification (either `open` or target it by ID) that's required for the Capacity Reservation that you created in the Local Zone. For more information, see [Launch instances into an existing Capacity Reservation](capacity-reservations-launch.md). # Capacity Reservations in Wavelength Zones *AWS Wavelength* enables developers to build applications that deliver ultra-low latencies to mobile devices and end users. Wavelength deploys standard AWS compute and storage services to the edge of telecommunication carriers' 5G networks. You can extend an Amazon Virtual Private Cloud (VPC) to one or more Wavelength Zones. You can then use AWS resources like Amazon EC2 instances to run applications that require ultra-low latency and a connection to AWS services in the Region. For more information, see [AWS Wavelength Zones](https://aws.amazon.com//wavelength/). When you create On-Demand Capacity Reservations, you can choose the Wavelength Zone and you can launch instances into a Capacity Reservation in a Wavelength Zone by specifying the subnet associated with the Wavelength Zone. A Wavelength Zone is represented by an AWS Region code followed by an identifier that indicates the location, for example `us-east-1-wl1-bos-wlz-1`. Wavelength Zones are not available in every Region. For information about the Regions that support Wavelength Zones, see [Available Wavelength Zones](https://docs.aws.amazon.com/wavelength/latest/developerguide/wavelength-quotas.html) in the *AWS Wavelength Developer Guide*. **Considerations** You can't use Capacity Reservation groups in a Wavelength Zone. **To use a Capacity Reservation in a Wavelength Zone** 1. Enable the Wavelength Zone for use in your AWS account. For more information, see [Get started with AWS Wavelength](https://docs.aws.amazon.com/wavelength/latest/developerguide/get-started-wavelength.html) in the *AWS Wavelength Developer Guide*. 1. Create a Capacity Reservation in the Wavelength Zone. For **Availability Zone**, choose the Wavelength. The Wavelength is represented by an AWS Region code followed by an identifier that indicates the location, for example `us-east-1-wl1-bos-wlz-1`. For more information, see [Create a Capacity Reservation](capacity-reservations-create.md). 1. Create a subnet in the Wavelength Zone. For **Availability Zone**, choose the Wavelength Zone. For more information, see [Create a subnet in your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/create-subnets.html) in the *Amazon VPC User Guide*. 1. Launch an instance. For **Subnet**, choose the subnet in the Wavelength Zone (for example `subnet-123abc | us-east-1-wl1-bos-wlz-1`), and for **Capacity Reservation**, choose the specification (either `open` or target it by ID) that's required for the Capacity Reservation that you created in the Wavelength. For more information, see [Launch instances into an existing Capacity Reservation](capacity-reservations-launch.md). # Capacity Reservations on AWS Outposts AWS Outposts is a fully managed service that extends AWS infrastructure, services, APIs, and tools to customer premises. By providing local access to AWS managed infrastructure, AWS Outposts enables customers to build and run applications on premises using the same programming interfaces as in AWS Regions, while using local compute and storage resources for lower latency and local data processing needs. An Outpost is a pool of AWS compute and storage capacity deployed at a customer site. AWS operates, monitors, and manages this capacity as part of an AWS Region. You can create Capacity Reservations on Outposts that you have created in your account. This allows you to reserve compute capacity on an Outpost at your site. You create and use Capacity Reservations on Outposts in the same way that you create and use Capacity Reservations in regular Availability Zones. The same features and instance matching behavior apply. You can also share Capacity Reservations on Outposts with other AWS accounts within your organization using AWS Resource Access Manager. For more information about sharing Capacity Reservations, see [Shared Capacity Reservations](capacity-reservation-sharing.md). **Prerequisite** You must have an Outpost installed at your site. For more information, see [ Create an Outpost and order Outpost capacity](https://docs.aws.amazon.com/outposts/latest/userguide/order-outpost-capacity.html) in the *AWS Outposts User Guide*. **Considerations** + You can't use Capacity Reservation groups on an Outpost. **To use a Capacity Reservation on an Outpost** 1. Create a subnet on the Outpost. For more information, see [Create a subnet](https://docs.aws.amazon.com/outposts/latest/userguide/launch-instance.html#create-subnet) in the *AWS Outposts User Guide*. 1. Create a Capacity Reservation on the Outpost. 1. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home). 1. In the navigation pane, choose **Outposts**, and then choose **Actions**, **Create Capacity Reservation**. 1. Configure the Capacity Reservation as needed and then choose **Create**. For more information, see [Create a Capacity Reservation](capacity-reservations-create.md). **Note** The **Instance Type** drop-down lists only instance types that are supported by the selected Outpost, and the **Availability Zone** drop-down lists only the Availability Zone with which the selected Outpost is associated. 1. Launch an instance into the Capacity Reservation. For **Subnet** choose the subnet that you created in Step 1, and for **Capacity Reservation**, select the Capacity Reservation that you created in Step 2. For more information, see [Launch an instance on the Outpost](https://docs.aws.amazon.com/outposts/latest/userguide/launch-instance.html#launch-instances) in the *AWS Outposts User Guide*. # Shared Capacity Reservations Capacity Reservation sharing enables Capacity Reservation owners to share their reserved capacity with other AWS accounts or within an AWS organization. This enables you to create and manage Capacity Reservations centrally, and share the reserved capacity across multiple AWS accounts or within your AWS organization. In this model, the AWS account that owns the Capacity Reservation (owner) shares it with other AWS accounts (consumers). Consumers can launch instances into Capacity Reservations that are shared with them in the same way that they launch instances into Capacity Reservations that they own in their own account. The Capacity Reservation owner is responsible for managing the Capacity Reservation and the instances that they launch into it. Owners cannot modify instances that consumers launch into Capacity Reservations that they have shared. Consumers are responsible for managing the instances that they launch into Capacity Reservations shared with them. Consumers cannot view or modify instances owned by other consumers or by the Capacity Reservation owner. A Capacity Reservation owner can share a Capacity Reservation with: + Specific AWS accounts inside or outside of its AWS organization + An organizational unit inside its AWS organization + Its entire AWS organization ## Prerequisites for sharing Capacity Reservations + To share a Capacity Reservation, you must own it in your AWS account. You cannot share a Capacity Reservation that has been shared with you. + You can only share Capacity Reservations for shared tenancy instances. You cannot share Capacity Reservations for dedicated tenancy instances. + Capacity Reservation sharing is not available to new AWS accounts or AWS accounts that have a limited billing history. + To share a Capacity Reservation with your AWS organization or an organizational unit in your AWS organization, you must enable sharing with AWS Organizations. For more information, see [Enable Sharing with AWS Organizations](https://docs.aws.amazon.com/ram/latest/userguide/getting-started-sharing.html) in the *AWS RAM User Guide*. + You can share a Capacity Reservation in `active` or `scheduled` state. You cannot share Capacity Reservation in other [ states ](https://docs.aws.amazon.com/cli/latest/reference/ec2/purchase-capacity-block.html), such as `assessing` or `unsupported`. ## Related services Capacity Reservation sharing integrates with AWS Resource Access Manager (AWS RAM). AWS RAM is a service that enables you to share your AWS resources with any AWS account or through AWS Organizations. With AWS RAM, you share resources that you own by creating a *resource share*. A resource share specifies the resources to share, and the consumers with whom to share them. Consumers can be individual AWS accounts, or organizational units or an entire organization from AWS Organizations. For more information about AWS RAM, see the *[AWS RAM User Guide](https://docs.aws.amazon.com/ram/latest/userguide/)*. ## Share across Availability Zones To ensure that resources are distributed across the Availability Zones for a Region, we independently map Availability Zones to names for each account. This could lead to Availability Zone naming differences across accounts. For example, the Availability Zone `us-east-1a` for your AWS account might not have the same location as `us-east-1a` for another AWS account. To identify the location of your Capacity Reservations relative to your accounts, you must use the *Availability Zone ID* (AZ ID). The AZ ID is a unique and consistent identifier for an Availability Zone across all AWS accounts. For example, `use1-az1` is an AZ ID for the `us-east-1` Region and it is the same location in every AWS account. When you share a Capacity Reservation with another account, the Capacity Reservation is associated with a specific location identified by its AZ ID. The consumer account can use the shared Capacity Reservation only in the Availability Zone that maps to the same AZ ID in their account. For example, if you create a Capacity Reservation in `us-east-1a` (AZ ID `use1-az1`), the consumer must launch instances in the Availability Zone that maps to `use1-az1` in their account. That Availability Zone might have a different name, such as `us-east-1b`. **To view the AZ IDs for the Availability Zones in your account** 1. Open the AWS RAM console at [https://console.aws.amazon.com/ram/home](https://console.aws.amazon.com/ram/home). 1. The AZ IDs for the current Region are displayed in the **Your AZ ID** panel on the right-hand side of the screen. # Share a Capacity Reservation When you share a Capacity Reservation that you own with other AWS accounts, you enable them to launch instances into your reserved capacity. If you share an open Capacity Reservation, keep the following in mind as it could lead to unintended Capacity Reservation usage: + If consumers have running instances that match the attributes of the Capacity Reservation, have the `CapacityReservationPreference` parameter set to `open`, and are not yet running in reserved capacity, they automatically use the shared Capacity Reservation. + If consumers launch instances that have matching attributes (instance type, platform, Availability Zone, and tenancy) and have the `CapacityReservationPreference` parameter set to `open`, they automatically launch into the shared Capacity Reservation. To share a Capacity Reservation, you must add it to a resource share. A resource share is an AWS RAM resource that lets you share your resources across AWS accounts. A resource share specifies the resources to share, and the consumers with whom they are shared. When you share a Capacity Reservation using the Amazon EC2 console, you add it to an existing resource share. To add the Capacity Reservation to a new resource share, you must create the resource share using the [AWS RAM console](https://console.aws.amazon.com/ram). If you are part of an organization in AWS Organizations and sharing within your organization is enabled, consumers in your organization are granted access to the shared Capacity Reservation if the [prerequisites for sharing](capacity-reservation-sharing.md#sharing-cr-prereq) are met. If the Capacity Reservation is shared with external accounts, they receive an invitation to join the resource share and are granted access to the shared Capacity Reservation after accepting the invitation. **Important** Before launching instances into a Capacity Reservation that is shared with you, verify that you have access to the shared Capacity Reservation by viewing it in the console or by describing it using the [ describe-capacity-reservations](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-capacity-reservations.html) AWS CLI command. If you can view the shared Capacity Reservation in the console or describe it using the AWS CLI, it is available for your use and you can launch instances into it. If you attempt to launch instances into the Capacity Reservation and it is not accessible due to a sharing failure, the instances will launch into On-Demand capacity. ------ #### [ Console ] **To share a Capacity Reservation that you own using the Amazon EC2 console** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation pane, choose **Capacity Reservations**. 1. Choose the Capacity Reservation to share and choose **Actions**, **Share reservation**. 1. Select the resource share to which to add the Capacity Reservation and choose **Share Capacity Reservation**. It could take a few minutes for consumers to get access to the shared Capacity Reservation. **To share a Capacity Reservation that you own using the AWS RAM console** See [Creating a resource share](https://docs.aws.amazon.com/ram/latest/userguide/working-with-sharing.html#working-with-sharing-create) in the *AWS RAM User Guide*. ------ #### [ AWS CLI ] **To share a Capacity Reservation that you own** Use the [create-resource-share](https://docs.aws.amazon.com/cli/latest/reference/ram/create-resource-share.html) command. ``` aws ram create-resource-share \ --name my-resource-share \ --resource-arns arn:aws:ec2:us-east-2:123456789012:capacity-reservation/cr-1234abcd56EXAMPLE ``` ------ #### [ PowerShell ] **To share a Capacity Reservation that you own** Use the [New-RAMResourceShare](https://docs.aws.amazon.com/powershell/latest/reference/items/New-RAMResourceShare.html) cmdlet. ``` New-RAMResourceShare ` -Name my-resource-share ` -ResourceArn "arn:aws:ec2:us-east-2:123456789012:capacity-reservation/cr-1234abcd56EXAMPLE" ``` ------ # Stop sharing a Capacity Reservation The Capacity Reservation owner can stop sharing a Capacity Reservation at any time. The following rules apply: + Instances owned by consumers that were running in the shared capacity at the time sharing stops continue to run normally outside of the reserved capacity, and the capacity is restored to the Capacity Reservation subject to Amazon EC2 capacity availability. + Consumers with whom the Capacity Reservation was shared can no longer launch new instances into the reserved capacity. To stop sharing a Capacity Reservation that you own, you must remove it from the resource share. ------ #### [ Console ] **To stop sharing a Capacity Reservation that you own using the Amazon EC2 console** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation pane, choose **Capacity Reservations**. 1. Select the Capacity Reservation and choose the **Sharing** tab. 1. The **Sharing** tab lists the resource shares to which the Capacity Reservation has been added. Select the resource share from which to remove the Capacity Reservation and choose **Remove from resource share**. **To stop sharing a Capacity Reservation that you own using the AWS RAM console** See [Updating a Resource Share](https://docs.aws.amazon.com/ram/latest/userguide/working-with-sharing.html#working-with-sharing-update) in the *AWS RAM User Guide*. ------ #### [ AWS CLI ] **To stop sharing a Capacity Reservation that you own** Use the [disassociate-resource-share](https://docs.aws.amazon.com/cli/latest/reference/ram/disassociate-resource-share.html) command. ``` aws ram disassociate-resource-share \ --resource-share-arn arn:aws:ram:us-east-2:123456789012:resource-share/7ab63972-b505-7e2a-420d-6f5d3EXAMPLE \ --resource-arns arn:aws:ec2:us-east-2:123456789012:capacity-reservation/cr-1234abcd56EXAMPLE ``` ------ #### [ PowerShell ] **To stop sharing a Capacity Reservation that you own** Use the [Disconnect-RAMResourceShare](https://docs.aws.amazon.com/powershell/latest/reference/items/Disconnect-RAMResourceShare.html) cmdlet. ``` Disconnect-RAMResourceShare ` -ResourceShareArn "arn:aws:ram:us-east-2:123456789012:resource-share/7ab63972-b505-7e2a-420d-6f5d3EXAMPLE" ` -ResourceArn "arn:aws:ec2:us-east-2:123456789012:capacity-reservation/cr-1234abcd56EXAMPLE" ``` ------ # Billing assignment for shared Amazon EC2 Capacity Reservations Billing assignment By default, when a Capacity Reservation is shared, the owner is billed for the instances they run in the Capacity Reservation and for any available capacity, also called *unused capacity*, in the Capacity Reservation; while consumers are billed only for the instances they run in the shared Capacity Reservation. If needed, the Capacity Reservation owner can assign the billing of any available capacity in the Capacity Reservation to any one of the accounts with which the Capacity Reservation is shared. After billing is assigned to another account, that account becomes the *billing owner* of any available capacity in the Capacity Reservation. Any charges for available capacity in the Capacity Reservation, from that point onward, are billed to the assigned account instead of the owner's account. The Capacity Reservation owner and the accounts with which the Capacity Reservation is shared continue to be billed for the instances they run in the Capacity Reservation. **Important** The Capacity Reservation owner remains the resource owner and they remain responsible for managing the Capacity Reservation. The account to which billing is assigned does not get any additional privileges; they can't cancel, modify, or share the Capacity Reservation in any way. **Topics** + [ ## How it works ](#how-billing-ownership-works) + [ ## Considerations ](#billing-ownership-considerations) + [Assign billing](request-billing-transfer.md) + [View billing assignment requests](view-billing-transfers.md) + [Accept or reject billing](accept-decline-billing-transfer.md) + [Cancel or revoke requests](cancel-billing-transfer.md) + [Monitor requests](billing-ownership-events.md) ## How it works Only the Capacity Reservation owner can assign billing of a shared Capacity Reservation to another account. Billing can be assigned only to an account with which the Capacity Reservation is shared and that is consolidated under the same AWS Organizations payer account as the Capacity Reservation owner. To assign billing of the available capacity of a Capacity Reservation to another account, the Capacity Reservation owner must initiate a request to the required account. The specified account receives the request and they must either accept or reject it within 12 hours. + If they **accept**, they become the *billing owner* of any available capacity, also called *unused capacity*, in the Capacity Reservation. From that point onward, charges for any available capacity in the Capacity Reservation are billed to their account instead of the owner's account. After it is accepted, only the Capacity Reservation owner can revoke billing from the assigned account. + If they **reject**, the Capacity Reservation owner remains the billing owner of the available capacity in the Capacity Reservation. Charges for any available capacity in the Capacity Reservation continue to be billed to the owner's account. + If they **do not accept or reject** the request within 12 hours, it expires and charges for any available capacity in the Capacity Reservation continue to be billed to owner's account. For the period that billing is assigned to another account, the `Reservation` and `UnusedBox` line items appear in the assigned account's Cost and Usage Report (CUR) instead of the owner's CUR. The following table shows which line items appear in the CUR for the Capacity Reservation owner and consumer accounts **before** billing is assigned to another account. | Account | CUR line items before billing is assigned | | --- | --- | | Capacity Reservation owner | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/assign-billing.html) | | Consumer accounts with which the Capacity Reservation is shared | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/assign-billing.html) | The following table shows which line items appear in the CUR for the Capacity Reservation owner and consumer accounts **after** billing is assigned to another account. | Account | CUR line items after billing is assigned | | --- | --- | | Capacity Reservation owner | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/assign-billing.html) | | Consumer account to which billing is assigned | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/assign-billing.html) | | Other consumer accounts with which the Capacity Reservation is shared | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/assign-billing.html) | **Note** \$1 The `BoxUsage` line item appears in an account's CUR only if they have running instances in the Capacity Reservation. For more information about the CUR line items, see [Monitoring Capacity Reservations](https://docs.aws.amazon.com/cur/latest/userguide/monitor-ondemand-reservations.html). Use the Capacity Reservation ARN in the CUR to determine who owns the Capacity Reservation. If the ARN includes your AWS account ID, you are the Capacity Reservation owner. Otherwise, the Capacity Reservation is owned by a different account but billing is assigned to you. Cost allocation tags assigned to Capacity Reservation by the owner will not appear in the consumer account's CUR. Cost allocation tags appear in the Capacity Reservation owner's CUR only. ## Considerations Keep the following in mind when assigning billing of a shared Capacity Reservation: + You can't do partial or split billing assignments. Billing of all available capacity of a Capacity Reservation can be assigned to one account at a time. + The available capacity of a Capacity Reservation can change over time. This will impact billing for the assigned account. For example, available capacity can increase if the Capacity Reservation owner increases the size of the Capacity Reservation, or if other consumer accounts stop or terminate their instances running in the Capacity Reservation. + Billing can be assigned only to a consumer account that is consolidated under the same AWS Organizations payer account. Billing is automatically revoked from the consumer account if they leave the organization, or if the Capacity Reservation is no longer shared with them. + Only the Capacity Reservation owner can cancel a pending billing assignment request and revoke billing from an assigned account after the request has been accepted. # Assign billing of a shared EC2 Capacity Reservation to another account Assign billing To assign billing of the available capacity of a shared Capacity Reservation to another account, the Capacity Reservation owner must initiate a request to the required account. In the Amazon EC2 console, this request is called a *transfer request*. A Capacity Reservation owner can assign billing of the available capacity of Capacity Reservation to an account only if: + The Capacity Reservation is already shared with that account. + The account is consolidated under the same AWS Organizations payer account as the Capacity Reservation owner. Billing is assigned to the specified account only once they accept the request. When a Capacity Reservation owner initiates a request, an Amazon EventBridge event is sent to the requested account. For more information, see [Monitor billing assignment requests for shared Capacity Reservations](billing-ownership-events.md). ------ #### [ Console ] **To assign billing of a shared Capacity Reservation** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation panel, select **Capacity Reservations** and then choose the shared Capacity Reservation. 1. In the **Billing of available capacity** section, choose **Assign billing**. 1. In the **Assign billing** screen, select the consumer account to which to assign billing, and then choose **Request**. ------ #### [ AWS CLI ] **To assign billing of a shared Capacity Reservation** Use the [associate-capacity-reservation-billing-owner](https://docs.aws.amazon.com/cli/latest/reference/ec2/associate-capacity-reservation-billing-owner.html) command. For `--capacity-reservation-id`, specify the ID of the shared Capacity Reservation. For `--unused-reservation-billing-owner-id`, specify the ID of the AWS account to which to assign billing. ``` aws ec2 associate-capacity-reservation-billing-owner \ --capacity-reservation-id cr-01234567890abcdef \ --unused-reservation-billing-owner-id 123456789012 ``` ------ #### [ PowerShell ] **To assign billing of a shared Capacity Reservation** Use the [Register-EC2CapacityReservationBillingOwner](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2CapacityReservationBillingOwner.html) cmdlet. For `-CapacityReservationId`, specify the ID of the shared Capacity Reservation. For `-UnusedReservationBillingOwnerId`, specify the ID of the AWS account to which to assign billing. ``` Register-EC2CapacityReservationBillingOwner ` -CapacityReservationId cr-01234567890abcdef ` -UnusedReservationBillingOwnerId 123456789012 ``` ------ # View billing assignment requests for shared EC2 Capacity Reservations View billing assignment requests A Capacity Reservation owner can view only the most recent billing assignment request that they initiated. And consumer accounts can view only the most recent billing assignment requests sent to them. Requests can be viewed for 24 hours after they enter the `cancelled`, `expired`, or `revoked` state. After 24 hours, they can no longer be viewed. ------ #### [ Console ] **(Capacity Reservation owner) To view requests you initiated** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation panel, select **Capacity Reservations** and then choose the shared Capacity Reservation for which to view requests. 1. The **Billing of available capacity** section shows the most recent request and its current state. **(Consumer account) To requests sent to you** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation panel, select **Capacity Reservations**. 1. If you have pending requests, the **Pending billing assignment requests** banner appears at the top of the screen. If the banner does not appear, you do not have pending requests. To view the requests, choose **Review requests** in the banner. ------ #### [ AWS CLI ] **(Capacity Reservation owner) To view requests you initiated** Use the [describe-capacity-reservation-billing-requests](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-capacity-reservation-billing-requests.html) command. ``` aws ec2 describe-capacity-reservation-billing-requests \ --role odcr-owner ``` **(Consumer account) To view requests sent to you** Use the [describe-capacity-reservation-billing-requests](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-capacity-reservation-billing-requests.html) command. ``` aws ec2 describe-capacity-reservation-billing-requests \ --role unused-reservation-billing-owner ``` ------ #### [ PowerShell ] **(Capacity Reservation owner) To view requests you initiated** Use the [Get-EC2CapacityReservationBillingRequest](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2CapacityReservationBillingRequest.html) cmdlet. ``` Get-EC2CapacityReservationBillingRequest ` -Role odcr-owner ``` **(Consumer account) To view requests sent to you** Use the [Get-EC2CapacityReservationBillingRequest](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2CapacityReservationBillingRequest.html) cmdlet. ``` Get-EC2CapacityReservationBillingRequest ` -Role unused-reservation-billing-owner ``` ------ A request can be in one of the following states. | State | Description | | --- | --- | | pending | The request has not been accepted or rejected, but it has not yet expired. | | accepted | The request was accepted by the specified account. Billing of available capacity of the Capacity Reservation is assigned to the consumer account. | | rejected | The request was rejected by the consumer account. | | cancelled | The request was cancelled by the Capacity Reservation owner while it was in the pending state. | | revoked | Billing was revoked from the consumer account for one of the following reasons: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/view-billing-transfers.html) | | expired | The request expired because the consumer account did not accept or reject it within 12 hours. | # Accept or reject billing of a shared EC2 Capacity Reservation Accept or reject billing If you receive a billing assignment request for a Capacity Reservation that is shared with you, you can either accept or reject it. The request remains in the `pending` state until it is accepted or rejected. If you accept the request, it enters the `accepted` state, and billing of any available, or *unused*, capacity of that Capacity Reservation is assigned to your account from that point onward. After you accept a request, only the Capacity Reservation owner can revoke billing from your account. If you reject the request, it enters the `rejected` state, and billing of the available capacity of the Capacity Reservation remains assigned to the Capacity Reservation owner. Requests expire if they are not accepted or rejected within 12 hours. If a request expires, billing of any unused capacity of the Capacity Reservation remains assigned to the Capacity Reservation owner. When a request is accepted or rejected, an Amazon EventBridge event is sent to the Capacity Reservation owner's account. When a request expires, an Amazon EventBridge event is sent to the Capacity Reservation owner and the consumer account. For more information, see [Monitor billing assignment requests for shared Capacity Reservations](billing-ownership-events.md). ------ #### [ Console ] **To accept or reject a request** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation panel, select **Capacity Reservations**. 1. If you have pending requests, the **Pending billing assignment requests** banner appears at the top of the screen. If the banner does not appear, you do not have pending requests. To view the requests, choose **Review requests** in the banner. 1. Select the request to accept or reject, and then choose either **Accept** or **Reject**. ------ #### [ AWS CLI ] **To accept a request** Use the [accept-capacity-reservation-billing-ownership](https://docs.aws.amazon.com/cli/latest/reference/ec2/accept-capacity-reservation-billing-ownership.html) command. For `--capacity-reservation-id`, specify the ID of the Capacity Reservation for which to accept the request. ``` aws ec2 accept-capacity-reservation-billing-ownership \ --capacity-reservation-id cr-01234567890abcdef ``` **To reject a request** Use the [reject-capacity-reservation-billing-ownership](https://docs.aws.amazon.com/cli/latest/reference/ec2/reject-capacity-reservation-billing-ownership.html) command. For `--capacity-reservation-id`, specify the ID of the Capacity Reservation for which to reject the request. ``` aws ec2 reject-capacity-reservation-billing-ownership \ --capacity-reservation-id cr-01234567890abcdef ``` ------ #### [ PowerShell ] **To accept a request** Use the [Approve-EC2CapacityReservationBillingOwnership](https://docs.aws.amazon.com/powershell/latest/reference/items/Approve-EC2CapacityReservationBillingOwnership.html) cmdlet. ``` Approve-EC2CapacityReservationBillingOwnership ` -CapacityReservationId cr-01234567890abcdef ``` **To reject a request** Use the [Deny-EC2CapacityReservationBillingOwnership](https://docs.aws.amazon.com/powershell/latest/reference/items/Deny-EC2CapacityReservationBillingOwnership.html) cmdlet. ``` Deny-EC2CapacityReservationBillingOwnership ` -CapacityReservationId cr-01234567890abcdef ``` ------ # Cancel or revoke billing assignment requests for shared EC2 Capacity Reservations Cancel or revoke requests Only the Capacity Reservation owner can cancel a `pending` billing assignment request. If a pending request is cancelled, it enters the `cancelled` state and billing of any available, or *unused*, capacity of the Capacity Reservation remains assigned to Capacity Reservation owner. After a request is `accepted`, only the Capacity Reservation owner can revoke billing from the assigned account. If billing is revoked, the request enters the `revoked` state and billing of any available capacity of the Capacity Reservation is reassigned to Capacity Reservation owner. When a request is cancelled or revoked, Amazon EventBridge events are sent to the Capacity Reservation owner and specified consumer account. For more information, see [Monitor billing assignment requests for shared Capacity Reservations](billing-ownership-events.md). ------ #### [ Console ] **To cancel or revoke a request** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation panel, select **Capacity Reservations** and then choose the Capacity Reservation for which to cancel or revoke the request. 1. In the **Billing of available capacity** section, choose **Cancel transfer** or **Revoke transfer**, depending on the current state of the request. ------ #### [ AWS CLI ] **To cancel or revoke a request** Use the [disassociate-capacity-reservation-billing-owner](https://docs.aws.amazon.com/cli/latest/reference/ec2/disassociate-capacity-reservation-billing-owner.html) command. For `--unused-reservation-billing-owner-id`, specify the ID of the AWS account to which the request was sent. ``` aws ec2 disassociate-capacity-reservation-billing-owner \ --capacity-reservation-id cr-01234567890abcdef \ --unused-reservation-billing-owner-id 123456789012 ``` ------ #### [ PowerShell ] **To cancel or revoke a request** Use the [Unregister-EC2CapacityReservationBillingOwner](https://docs.aws.amazon.com/powershell/latest/reference/items/Unregister-EC2CapacityReservationBillingOwner.html) cmdlet. For `-UnusedReservationBillingOwnerId`, specify the ID of the AWS account to which the request was sent. ``` Unregister-EC2CapacityReservationBillingOwner ` -CapacityReservationId cr-01234567890abcdef ` -UnusedReservationBillingOwnerId 123456789012 ``` ------ # Monitor billing assignment requests for shared Capacity Reservations Monitor requests Amazon EC2 sends Amazon EventBridge events when the state of a billing assignment request changes. + Events are sent to the Capacity Reservation owner when a request enters the following states: `accepted` \$1 `rejected` \$1 `expired` \$1 `revoked`. + Events are sent to the requested consumer account when a request enters the following states: `pending` \$1 `expired` \$1 `cancelled` \$1 `revoked`. For more information about Amazon EventBridge, see the [ Amazon EventBridge User Guide](https://docs.aws.amazon.com/eventbridge/latest/userguide/). The following is the Amazon EventBridge event pattern. ``` { "version":"0", "id":"12345678-1234-1234-1234-123456789012", "detail-type":"On-Demand Capacity Reservation Billing Ownership Request pending|accepted|rejected|cancelled|revoked|expired", "source":"aws.ec2", "account":"account_id", "time":"state_change_timestamp", "region":"region", "resources":[ "arn:aws:ec2:region:cr_owner_account_id:capacity-reservation/cr_id" ], "detail":{ "capacity-reservation-id":"cr_id", "updateTime":timestamp, "ownerAccountId":"cr_owner_account_id", "unusedReservationChargesOwnerID":"consumer_account_id", "status":"pending|accepted|rejected|cancelled|revoked|expired", "statusMessage":"message } } ``` The following is an example of an event that is sent to the Capacity Reservation owner (`222222222222`) when a consumer account (`111111111111`) accepts a billing assignment request for a shared Capacity Reservation (`cr-01234567890abcdef`). ``` { "version":"0", "id":"12345678-1234-1234-1234-123456789012", "detail-type":"On-Demand Capacity Reservation Billing Ownership Request accepted", "source":"aws.ec2", "account":"222222222222", "time":"2024-09-01Thh:59:59Z", "region":"us-east-1", "resources":[ "arn:aws:ec2:us-east-1:222222222222:capacity-reservation/cr-01234567890abcdef" ], "detail":{ "capacity-reservation-id":"cr-01234567890abcdef", "updateTime":"2024-08-01Thh:59:59Z", "ownerAccountId":"222222222222", "unusedReservationChargesOwnerID":"111111111111", "status":"accepted", "statusMessage":"billing transfer status message" } } ``` ## Shared Capacity Reservation permissions ### Permissions for owners Owners are responsible for managing and canceling their shared Capacity Reservations. Owners cannot modify instances running in the shared Capacity Reservation that are owned by other accounts. Owners remain responsible for managing instances that they launch into the shared Capacity Reservation. ### Permissions for consumers Consumers are responsible for managing their instances that are running the shared Capacity Reservation. Consumers cannot modify the shared Capacity Reservation in any way, and they cannot view or modify instances that are owned by other consumers or the Capacity Reservation owner. Consumers can only view the total capacity and available capacity in the shared reservation. ## Billing and metering There are no additional charges for sharing Capacity Reservations. By default, the Capacity Reservation owner is billed for instances that they run inside the Capacity Reservation and for unused reserved capacity, while consumers are billed for the instances that they run inside the shared Capacity Reservation. However, you can assign billing of the available capacity of a shared Capacity Reservation to a specific consumer account. For more information, see [Billing assignment for shared Amazon EC2 Capacity Reservations](assign-billing.md). If the Capacity Reservation owner belongs to a different payer account and the Capacity Reservation is covered by a Regional Reserved Instance or a Savings Plan, the Capacity Reservation owner continues to be billed for the Regional Reserved Instance or Savings Plan. In these cases, the Capacity Reservation owner pays for the Regional Reserved Instance or Savings Plan, and consumers are billed for the instances that the run in the shared Capacity Reservation. ## Instance limits All Capacity Reservation usage counts toward the Capacity Reservation owner's On-Demand Instance limits. This includes: + Unused reserved capacity + Usage by instances owned by the Capacity Reservation owner + Usage by instances owned by consumers Instances launched into the shared capacity by consumers count towards the Capacity Reservation owner's On-Demand Instance limit. Consumers' instance limits are a sum of their own On-Demand Instance limits and the capacity available in the shared Capacity Reservations to which they have access. # Capacity Reservation Fleets An *On-Demand Capacity Reservation Fleet* is a group of Capacity Reservations. A Capacity Reservation Fleet request contains all of the configuration information that's needed to launch a Capacity Reservation Fleet. Using a single request, you can reserve large amounts of Amazon EC2 capacity for your workload across multiple instance types, up to a target capacity that you specify. After you create a Capacity Reservation Fleet, you can manage the Capacity Reservations in the fleet collectively by modifying or canceling the Capacity Reservation Fleet. **Topics** + [ ## How Capacity Reservation Fleets work ](#cr-how-it-works) + [ ## Considerations ](#considerations) + [ ## Pricing ](#pricing) + [Concepts and planning](crfleet-concepts.md) + [Create](create-crfleet.md) + [Modify](modify-crfleet.md) + [Cancel](cancel-crfleet.md) + [Example configurations](crfleet-example-configs.md) + [Using service-linked roles](using-service-linked-roles.md) ## How Capacity Reservation Fleets work When you create a Capacity Reservation Fleet, the Fleet attempts to create individual Capacity Reservations to meet the total target capacity that you specified in the Fleet request. The number of instances for which the Fleet reserves capacity depends on the [*total target capacity*](crfleet-concepts.md#target-capacity) and the [*instance type weights*](crfleet-concepts.md#instance-weight) that you specify. The instance type for which it reserves capacity depends on the [*allocation strategy*](crfleet-concepts.md#allocation-strategy) and [*instance type priorities*](crfleet-concepts.md#instance-priority) that you use. If there is insufficient capacity at the time the Fleet is created, and it is unable to immediately meet its total target capacity, the Fleet asynchronously attempts to create Capacity Reservations until it has reserved the requested amount of capacity. When the Fleet reaches its total target capacity, it attempts to maintain that capacity. If a Capacity Reservation in the Fleet is cancelled, the Fleet automatically creates one or more Capacity Reservations, depending on your Fleet configuration, to replace the lost capacity and to maintain its total target capacity. The Capacity Reservations in the Fleet can't be managed individually. They must be managed collectively by modifying the Fleet. When you modify a Fleet, the Capacity Reservations in the Fleet are automatically updated to reflect the changes. Currently, Capacity Reservation Fleets support the `open` instance matching criteria, and all Capacity Reservations launched by a Fleet automatically use this instance matching criteria. With this criteria, new instances and existing instances that have matching attributes (instance type, platform, Availability Zone, and tenancy) automatically run in the Capacity Reservations created by a Fleet. Capacity Reservation Fleets do not support targeted instance matching criteria. ## Considerations Keep the following in mind when working with Capacity Reservation Fleets: + A Capacity Reservation Fleet can be created, modified, viewed, and cancelled using the AWS CLI and AWS API. + The Capacity Reservations in a Fleet can't be managed individually. They must be managed collectively by modifying or cancelling the Fleet. + A Capacity Reservation Fleet can't span across Regions. + A Capacity Reservation Fleet can't span across Availability Zones. + Capacity Reservations created by a Capacity Reservation Fleet are automatically tagged with the following AWS generated tag: + Key — `aws:ec2-capacity-reservation-fleet` + Value — `fleet_id` You can use this tag to identify Capacity Reservations that were created by a Capacity Reservation Fleet. ## Pricing There are no additional charges for using Capacity Reservation Fleets. You are billed for the individual Capacity Reservations that are created by your Capacity Reservation Fleets. For more information about how Capacity Reservations are billed, see [Capacity Reservation pricing and billing](capacity-reservations-pricing-billing.md). # Capacity Reservation Fleet concepts and planning Concepts and planning The following information describes how to plan a Capacity Reservation Fleet and describes Capacity Reservation Fleet concepts including total target capacity, allocation strategy, instance type weight, and instance type priority. **Topics** + [ ## Plan a Capacity Reservation Fleet ](#plan-cr-fleet) + [ ## Total target capacity ](#target-capacity) + [ ## Allocation strategy ](#allocation-strategy) + [ ## Instance type weight ](#instance-weight) + [ ## Instance type priority ](#instance-priority) ## Plan a Capacity Reservation Fleet When planning your Capacity Reservation Fleet, we recommend that you do the following: 1. Determine the amount of compute capacity that is needed by your workload. 1. Decide on the instance types and Availability Zones that you want to use. 1. Assign each instance type a priority based on your needs and preferences. For more information, see [Instance type priority](#instance-priority). 1. Create a capacity weighting system that makes sense for your workload. Assign a weight to each instance type and determine your total target capacity. For more information, see [Instance type weight](#instance-weight) and [Total target capacity](#target-capacity). 1. Determine whether you need the Capacity Reservation indefinitely or only for a specific period of time. ## Total target capacity The *total target capacity* defines the total amount of compute capacity that the Capacity Reservation Fleet reserves. You specify the total target capacity when you create the Capacity Reservation Fleet. After the Fleet has been created, Amazon EC2 automatically creates Capacity Reservations to reserve capacity up to the total target capacity. The number of instances for which the Capacity Reservation Fleet reserves capacity is determined by the total target capacity and the *instance type weight* that you specify for each instance type in the Capacity Reservation Fleet (`total target capacity`/`instance type weight`=`number of instances`). You can assign a total target capacity based on units that are meaningful to your workload. For example, if your workload requires a certain number of vCPUs, you can assign the total target capacity based on the number of vCPUs required. If your workload requires `2048` vCPUs, specify a total target capacity of `2048` and then assign instance type weights based on the number of vCPUs provided by the instance types in the Fleet. For an example, see [Instance type weight](#instance-weight). ## Allocation strategy The allocation strategy for your Capacity Reservation Fleet determines how it fulfills your request for reserved capacity from the instance type specifications in the Capacity Reservation Fleet configuration. Currently, only the `prioritized` allocation strategy is supported. With this strategy, the Capacity Reservation Fleet creates Capacity Reservations using the priorities that you have assigned to each of the instance type specifications in the Capacity Reservation Fleet configuration. Lower priority values indicate higher priority for use. For example, say you create a Capacity Reservation Fleet that uses the following instance types and priorities: + `m4.16xlarge` — priority = 1 + `m5.16xlarge` — priority = 3 + `m5.24xlarge` — priority = 2 The Fleet first attempts to create Capacity Reservations for `m4.16xlarge`. If Amazon EC2 has insufficient `m4.16xlarge` capacity, the Fleet attempts to create Capacity Reservations for `m5.24xlarge`. If Amazon EC2 has insufficient `m5.24xlarge` capacity, the Fleet creates Capacity Reservations for `m5.16xlarge`. ## Instance type weight The *instance type weight* is a weight that you assign to each instance type in the Capacity Reservation Fleet. The weight determines how many units of capacity each instance of that specific instance type counts toward the Fleet's *total target capacity*. You can assign weights based on units that are meaningful to your workload. For example, if your workload requires a certain number of vCPUs, you can assign weights based on the number of vCPUs provided by each instance type in the Capacity Reservation Fleet. In this case, if you create a Capacity Reservation Fleet using `m4.16xlarge` and `m5.24xlarge` instances, you would assign weights that correspond to the number of vCPUs for each instance as follows: + `m4.16xlarge` — `64` vCPUs, weight = `64` units + `m5.24xlarge` — `96` vCPUs, weight = `96` units The instance type weight determines the number of instances for which the Capacity Reservation Fleet reserves capacity. For example, if a Capacity Reservation Fleet with a total target capacity of `384` units uses the instance types and weights in the preceding example, the Fleet could reserve capacity for `6` `m4.16xlarge` instances (384 total target capacity/64 instance type weight=6 instances), or `4` `m5.24xlarge` instances (384 / 96 = 4). If you do not assign instance type weights, or if you assign an instance type weight of `1`, the total target capacity is based purely on instance count. For example, if a Capacity Reservation Fleet with a total target capacity of `384` units uses the instance types in the preceding example, but omits the weights or specifies a weight of `1` for both instance types, the Fleet could reserve capacity for either `384` `m4.16xlarge` instances or `384` `m5.24xlarge` instances. ## Instance type priority The *instance type priority* is a value that you assign to the instance types in the Fleet. The priorities are used to determine which of the instance types specified for the Fleet should be prioritized for use. Lower priority values indicate a higher priority for use. # Create a Capacity Reservation Fleet Create When you create a Capacity Reservation Fleet it automatically creates Capacity Reservations for the instance types specified in the Fleet request, up to the specified total target capacity. The number of instances for which the Capacity Reservation Fleet reserves capacity depends on the total target capacity and instance type weights that you specify in the request. For more information, see [Instance type weight](crfleet-concepts.md#instance-weight) and [Total target capacity](crfleet-concepts.md#target-capacity). When you create the Fleet, you must specify the instance types to use and a priority for each of those instance types. For more information, see [Allocation strategy](crfleet-concepts.md#allocation-strategy) and [Instance type priority](crfleet-concepts.md#instance-priority). **Note** The **AWSServiceRoleForEC2CapacityReservationFleet** service-linked role is automatically created in your account the first time that you create a Capacity Reservation Fleet. For more information, see [Using service-linked roles for Capacity Reservation FleetUsing service-linked roles for EC2 Capacity Manager](using-service-linked-roles.md). Currently, Capacity Reservation Fleets support the `open` instance matching criteria only. ------ #### [ AWS CLI ] **To create a Capacity Reservation Fleet** Use the [create-capacity-reservation-fleet](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-capacity-reservation-fleet.html) command. ``` aws ec2 create-capacity-reservation-fleet \ --total-target-capacity 24 \ --allocation-strategy prioritized \ --instance-match-criteria open \ --tenancy default \ --end-date 2021-12-31T23:59:59.000Z \ --instance-type-specifications file://instanceTypeSpecification.json ``` The following are the contents of `instanceTypeSpecification.json`. ``` [ { "InstanceType": "m5.xlarge", "InstancePlatform": "Linux/UNIX", "Weight": 3.0, "AvailabilityZone":"us-east-1a", "EbsOptimized": true, "Priority" : 1 } ] ``` The following is example output. ``` { "Status": "submitted", "TotalFulfilledCapacity": 0.0, "CapacityReservationFleetId": "crf-abcdef01234567890", "TotalTargetCapacity": 24 } ``` ------ #### [ PowerShell ] **To create a Capacity Reservation Fleet** Use the [New-EC2CapacityReservationFleet](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2CapacityReservationFleet.html) cmdlet. ``` New-EC2CapacityReservationFleet ` -TotalTargetCapacity 24 ` -AllocationStrategy "prioritized" ` -InstanceMatchCriterion "open" ` -Tenancy "default" ` -EndDate 2021-12-31T23:59:59.000Z ` -InstanceTypeSpecification $specification ``` The specification is defined as follows. ``` $specification = New-Object Amazon.EC2.Model.ReservationFleetInstanceSpecification $specification.InstanceType = "m5.xlarge" $specification.InstancePlatform = "Linux/UNIX" $specification.Weight = 3.0 $specification.AvailabilityZone = "us-east-1a" $specification.EbsOptimized = $true $specification.Priority = 1 ``` ------ # Modify a Capacity Reservation Fleet Modify You can modify the total target capacity and date of a Capacity Reservation Fleet at any time. When you modify the total target capacity of a Capacity Reservation Fleet, the Fleet automatically creates new Capacity Reservations, or modifies or cancels existing Capacity Reservations in the Fleet to meet the new total target capacity. When you modify the end date for the Fleet, the end dates for all of the individual Capacity Reservations are updated accordingly. **Considerations** + After you modify a Fleet, its status transitions to `modifying`. You can't attempt additional modifications to a Fleet while it is in the `modifying` state. + You can't modify the tenancy, Availability Zone, instance types, instance platforms, priorities, or weights used by a Capacity Reservation Fleet. If you need to change any of these parameters, you might need to cancel the existing Fleet and create a new one with the required parameters. + You can't specify `--end-date` and `--remove-end-date` in the same command. ------ #### [ AWS CLI ] **To modify a Capacity Reservation Fleet** Use the [modify-capacity-reservation-fleet](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-capacity-reservation-fleet.html) command. **Example 1: Modify total target capacity** ``` aws ec2 modify-capacity-reservation-fleet \ --capacity-reservation-fleet-id crf-01234567890abcedf \ --total-target-capacity 160 ``` **Example 2: Modify end date** ``` aws ec2 modify-capacity-reservation-fleet \ --capacity-reservation-fleet-id crf-01234567890abcedf \ --end-date 2021-07-04T23:59:59.000Z ``` **Example 3: Remove end date** ``` aws ec2 modify-capacity-reservation-fleet \ --capacity-reservation-fleet-id crf-01234567890abcedf \ --remove-end-date ``` ------ #### [ PowerShell ] **To modify a Capacity Reservation Fleet** Use the [Edit-EC2CapacityReservationFleet](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2CapacityReservationFleet.html) cmdlet. **Example 1: Modify total target capacity** ``` Edit-EC2CapacityReservationFleet ` -CapacityReservationFleetId crf-01234567890abcedf ` -TotalTargetCapacity 160 ``` **Example 2: Modify end date** ``` Edit-EC2CapacityReservationFleet ` -CapacityReservationFleetId crf-01234567890abcedf ` -EndDate 2021-07-04T23:59:59.000Z ``` **Example 3: Remove end date** ``` Edit-EC2CapacityReservationFleet ` -CapacityReservationFleetId crf-01234567890abcedf ` -RemoveEndDate ``` ------ # Cancel a Capacity Reservation Fleet Cancel When you no longer need a Capacity Reservation Fleet and the capacity it reserves, you can cancel it. When you cancel a Fleet, its status changes to `cancelled` and it can no longer create new Capacity Reservations. Additionally, all of the individual Capacity Reservations in the Fleet are canceled. The instances that were previously running in the reserved capacity continue to run normally in the shared capacity. ------ #### [ AWS CLI ] **To cancel a Capacity Reservation Fleet** Use the [cancel-capacity-reservation-fleets](https://docs.aws.amazon.com/cli/latest/reference/ec2/cancel-capacity-reservation-fleets.html) command. ``` aws ec2 cancel-capacity-reservation-fleets \ --capacity-reservation-fleet-ids crf-abcdef01234567890 ``` The following is example output. ``` { "SuccessfulFleetCancellations": [ { "CurrentFleetState": "cancelling", "PreviousFleetState": "active", "CapacityReservationFleetId": "crf-abcdef01234567890" } ], "FailedFleetCancellations": [] } ``` ------ #### [ PowerShell ] **To cancel a Capacity Reservation Fleet** Use the [Stop-EC2CapacityReservationFleet](https://docs.aws.amazon.com/powershell/latest/reference/items/Stop-EC2CapacityReservationFleet.html) cmdlet. ``` Stop-EC2CapacityReservationFleet ` -CapacityReservationFleetId crf-abcdef01234567890 ``` ------ # Example Capacity Reservation Fleet configurations Example configurations The following example creates a Capacity Reservation Fleet that uses two instance types: `m5.4xlarge` and `m5.12xlarge`. It uses a weighting system based on the number of vCPUs provided by the specified instance types. The total target capacity is `480` vCPUs. The `m5.4xlarge` provides 16 vCPUs and gets a weight of `16`, while the `m5.12xlarge` provides 48 vCPUs and gets a weight of `48`. This weighting system configures the Capacity Reservation Fleet to reserve capacity for either 30 `m5.4xlarge` instances (480/16=30), or 10 `m5.12xlarge` instances (480/48=10). The Fleet is configured to prioritize the `m5.12xlarge` capacity and gets priority of `1`, while the `m5.4xlarge` gets a lower priority of `2`. This means that the fleet will attempt to reserve the `m5.12xlarge` capacity first, and only attempt to reserve the `m5.4xlarge` capacity if Amazon EC2 has insufficient `m5.12xlarge` capacity. The Fleet reserves the capacity for `Windows` instances and the reservation automatically expires on `October 31, 2021` at `23:59:59` UTC. ``` aws ec2 create-capacity-reservation-fleet \ --total-target-capacity 480 \ --allocation-strategy prioritized \ --instance-match-criteria open \ --tenancy default \ --end-date 2021-10-31T23:59:59.000Z \ --instance-type-specifications file://instanceTypeSpecification.json ``` The following is the contents of `instanceTypeSpecification.json`. ``` [ { "InstanceType": "m5.4xlarge", "InstancePlatform":"Windows", "Weight": 16, "AvailabilityZone":"us-east-1a", "EbsOptimized": true, "Priority" : 2 }, { "InstanceType": "m5.12xlarge", "InstancePlatform":"Windows", "Weight": 48, "AvailabilityZone":"us-east-1a", "EbsOptimized": true, "Priority" : 1 } ] ``` # Using service-linked roles for Capacity Reservation Fleet Using service-linked roles On-Demand Capacity Reservation Fleet uses AWS Identity and Access Management (IAM) [service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html#id_roles_terms-and-concepts). A service-linked role is a unique type of IAM role that is linked directly to Capacity Reservation Fleet. Service-linked roles are predefined by Capacity Reservation Fleet and include all the permissions that the service requires to call other AWS services on your behalf. A service-linked role makes setting up Capacity Reservation Fleet easier because you don’t have to manually add the necessary permissions. Capacity Reservation Fleet defines the permissions of its service-linked roles, and unless defined otherwise, only Capacity Reservation Fleet can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy cannot be attached to any other IAM entity. You can delete a service-linked role only after first deleting their related resources. This protects your Capacity Reservation Fleet resources because you can't inadvertently remove permission to access the resources. ## Service-linked role permissions for Capacity Reservation Fleet Service-linked role permissions Capacity Reservation Fleet uses the service-linked role named **AWSServiceRoleForEC2CapacityReservationFleet** to create, describe, modify, and cancel Capacity Reservations in a Capacity Reservation Fleet on your behalf. The AWSServiceRoleForEC2CapacityReservationFleet service-linked role trusts the following entity to assume the role: + `capacity-reservation-fleet.amazonaws.com` The role uses the `AWSEC2CapacityReservationFleetRolePolicy` AWS managed policy. For more information, see [AWS managed policy: AWSEC2CapacityReservationFleetRolePolicy](security-iam-awsmanpol.md#security-iam-awsmanpol-AWSEC2CapacityReservationFleetRolePolicy). You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see [Service-linked role permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create-service-linked-role.html#service-linked-role-permissions) in the *IAM User Guide*. ## Create a service-linked role for Capacity Reservation Fleet Create a service-linked role You don't need to manually create a service-linked role. When you create a Capacity Reservation Fleet using the `create-capacity-reservation-fleet` AWS CLI command or the `CreateCapacityReservationFleet` API, the service-linked role is automatically created for you. If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you create a Capacity Reservation Fleet, Capacity Reservation Fleet creates the service-linked role for you again. ## Edit a service-linked role for Capacity Reservation Fleet Edit a service-linked role Capacity Reservation Fleet does not allow you to edit the AWSServiceRoleForEC2CapacityReservationFleet service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see [Edit a service-linked role description](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_update-service-linked-role.html#edit-service-linked-role-iam-console) in the *IAM User Guide*. ## Delete a service-linked role for Capacity Reservation Fleet Delete a service-linked role If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don’t have an unused entity that is not actively monitored or maintained. However, you must delete the resources for your service-linked role before you can manually delete it. **Note** If the Capacity Reservation Fleet service is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again. **To delete the AWSServiceRoleForEC2CapacityReservationFleet service-linked role** 1. Use the `delete-capacity-reservation-fleet` AWS CLI command or the `DeleteCapacityReservationFleet` API to delete the Capacity Reservation Fleets in your account. 1. Use the IAM console, the AWS CLI, or the AWS API to delete the AWSServiceRoleForEC2CapacityReservationFleet service-linked role. For more information, see [Delete a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage_delete.html#id_roles_manage_delete_slr) in the *IAM User Guide*. ## Supported Regions for Capacity Reservation Fleet service-linked roles Supported Regions Capacity Reservation Fleet supports using service-linked roles in all of the Regions where the service is available. For more information, see [AWS Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/ec2-service.html#ec2_region). # Monitor Capacity Reservations usage with CloudWatch metrics Monitor with CloudWatch metrics With CloudWatch metrics, you can efficiently monitor your Capacity Reservations and identify unused capacity by setting CloudWatch alarms to notify you when usage thresholds are met. This can help you maintain a constant Capacity Reservation volume and achieve a higher level of utilization. Capacity Reservations send metric data to CloudWatch every five minutes. Metrics are not supported for Capacity Reservations that are active for less than five minutes. For more information about viewing metrics in the CloudWatch console, see [Using Amazon CloudWatch Metrics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/working_with_metrics.html). For more information about creating alarms, see [Creating Amazon CloudWatch Alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html). **Topics** + [ ## Capacity Reservation usage metrics ](#capacity-reservation-usage-metrics) + [ ## Capacity Reservation metric dimensions ](#capacity-reservation-dimensions) + [ ## View CloudWatch metrics for Capacity Reservations ](#viewing-capacity-reservation-metrics) ## Capacity Reservation usage metrics The `AWS/EC2CapacityReservations` namespace includes the following usage metrics you can use to monitor and maintain on-demand capacity within thresholds you specify for your reservation. | Metric | Description | | --- | --- | | UsedInstanceCount | The number of instances that are currently in use. Unit: Count | | AvailableInstanceCount | The number of instances that are available. Unit: Count | | TotalInstanceCount | The total number of instances you have reserved. Unit: Count | | InstanceUtilization | The percentage of reserved capacity instances that are currently in use. Unit: Percent | ## Capacity Reservation metric dimensions You can use the following dimensions to refine the metrics listed in the previous table within the selected Region and account. | Dimension | Description | | --- | --- | | (No dimension) | This dimension filters the specified metric for all Capacity Reservations. | | CapacityReservationId | This dimension filters the specified metric for the identified Capacity Reservation. | | InstanceType | This dimension filters the specified metric for the identified instance type. | | AvailabilityZone | This dimension filters the specified metric for the identified Availability Zone. | | InstanceMatchCriteria | This dimension filters the specified metric for the identified instance match criteria (`open` or `targeted`). | | InstancePlatform | This dimension filters the specified metric data for the identified platform. | | Tenancy | This dimension filters the specified metric for the identified tenancy. | ## View CloudWatch metrics for Capacity Reservations Metrics are grouped first by the service namespace, and then by the supported dimensions. You can use the following procedures to view the metrics for your Capacity Reservations. **To view Capacity Reservation metrics using the CloudWatch console** 1. Open the CloudWatch console at [https://console.aws.amazon.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/). 1. If necessary, change the Region. From the navigation bar, select the Region where your Capacity Reservation resides. For more information, see [Regions and Endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html). 1. In the navigation pane, choose **Metrics**. 1. For **All metrics**, choose **EC2 Capacity Reservations**. 1. Choose from the preceding metric dimensions **Across All Capacity Reservations**, **By Capacity Reservation**, **By Instance Type**, **By Availability Zone**, **By Platform**, **By Instance Match Criteria** or **By Tenancy** and metrics will be grouped by No dimension, `CapacityReservationId`, `InstanceType`, `AvailabilityZone`, `Platform`, `InstanceMatchCriteria`, and `Tenancy` respectively. 1. To sort the metrics, use the column heading. To graph a metric, select the checkbox next to the metric. **To view Capacity Reservation metrics using the AWS CLI** Use the following [list-metrics](https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/list-metrics.html) command: ``` aws cloudwatch list-metrics --namespace "AWS/EC2CapacityReservations" ``` # Monitor Capacity Reservation underutilization Monitor underutilization You can monitor Capacity Reservation underutilization using the following: **Topics** + [ ## Amazon EventBridge events ](#cr-underutilization-events) + [ ## Email and AWS Health Dashboard notifications ](#monitor-cr-utilization) ## Amazon EventBridge events AWS Health sends events to Amazon EventBridge when a Capacity Reservation in your account is below 20 percent usage over certain periods. With EventBridge, you can establish rules that trigger programmatic actions in response to such events. For example, you can create a rule that automatically cancels a Capacity Reservation when its utilization drops below 20 percent utilization over a 7-day period. Events in EventBridge are represented as JSON objects. The fields that are unique to the event are contained in the "detail" section of the JSON object. The "event" field contains the event name. The "result" field contains the completed status of the action that triggered the event. For more information, see [Amazon EventBridge event patterns](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-event-patterns.html) in the *Amazon EventBridge User Guide*. For more information, see the [Amazon EventBridge User Guide](https://docs.aws.amazon.com/eventbridge/latest/userguide/). This feature is not supported in AWS GovCloud (US). ### Events AWS Health sends the following events when capacity usage for a Capacity Reservation is below 20 percent. + `AWS_EC2_ODCR_UNDERUTILIZATION_NOTIFICATION` The following is an example of an event that is generated when a newly created Capacity Reservation is below 20 percent capacity usage over a 24-hour period. ``` { "version": "0", "id": "b3e00086-f271-12a1-a36c-55e8ddaa130a", "detail-type": "AWS Health Event", "source": "aws.health", "account": "123456789012", "time": "2023-03-10T12:03:38Z", "region": "ap-south-1", "resources": [ "cr-01234567890abcdef" ], "detail": { "eventArn": "arn:aws:health:ap-south-1::event/EC2/AWS_EC2_ODCR_UNDERUTILIZATION_NOTIFICATION/AWS_EC2_ODCR_UNDERUTILIZATION_NOTIFICATION_cr-01234567890abcdef-6211-4d50-9286-0c9fbc243f04", "service": "EC2", "eventTypeCode": "AWS_EC2_ODCR_UNDERUTILIZATION_NOTIFICATION", "eventTypeCategory": "accountNotification", "startTime": "Fri, 10 Mar 2023 12:03:38 GMT", "endTime": "Fri, 10 Mar 2023 12:03:38 GMT", "eventDescription": [ { "language": "en_US", "latestDescription": "A description of the event will be provided here" } ], "affectedEntities": [ { "entityValue": "cr-01234567890abcdef" } ] } } ``` + `AWS_EC2_ODCR_UNDERUTILIZATION_NOTIFICATION_SUMMARY` The following is an example of an event that is generated when one or more Capacity Reservation is below 20 percent capacity usage over a 7-day period. ``` { "version": "0", "id":"7439d42b-3c7f-ad50-6a88-25e2a70977e2", "detail-type": "AWS Health Event", "source": "aws.health", "account": "123456789012", "time": "2023-03-07T06:06:01Z", "region": "us-east-1", "resources": [ "cr-01234567890abcdef | us-east-1b | t3.medium | Linux/UNIX | 0.0%", "cr-09876543210fedcba | us-east-1a | t3.medium | Linux/UNIX | 0.0%" ], "detail": { "eventArn": "arn:aws:health:us-east-1::event/EC2/AWS_EC2_ODCR_UNDERUTILIZATION_NOTIFICATION_SUMMARY/AWS_EC2_ODCR_UNDERUTILIZATION_NOTIFICATION_SUMMARY_726c1732-d6f6-4037-b9b8-bec3c2d3ba65", "service": "EC2", "eventTypeCode": "AWS_EC2_ODCR_UNDERUTILIZATION_NOTIFICATION_SUMMARY", "eventTypeCategory": "accountNotification", "startTime": "Tue, 7 Mar 2023 06:06:01 GMT", "endTime": "Tue, 7 Mar 2023 06:06:01 GMT", "eventDescription": [ { "language": "en_US", "latestDescription": "A description of the event will be provided here" } ], "affectedEntities": [ { "entityValue": "cr-01234567890abcdef | us-east-1b | t3.medium | Linux/UNIX | 0.0%" }, { "entityValue": "cr-09876543210fedcba | us-east-1a | t3.medium | Linux/UNIX | 0.0%" } ] } } ``` ### Create an EventBridge rule To receive email notifications when your Capacity Reservation utilization drops below 20 percent, create an Amazon SNS topic, and then create an EventBridge rule for the `AWS_EC2_ODCR_UNDERUTILIZATION_NOTIFICATION` event. **To create the Amazon SNS topic** 1. Open the Amazon SNS console at [https://console.aws.amazon.com/sns/v3/home](https://console.aws.amazon.com/sns/v3/home). 1. In the navigation pane, choose **Topics**, and then choose **Create topic**. 1. For **Type**, choose **Standard**. 1. For **Name**, enter a name for the new topic. 1. Choose **Create topic**. 1. Choose **Create subscription**. 1. For **Protocol**, choose **Email**, and then for **Endpoint**, enter the email address that receives the notifications. 1. Choose **Create subscription**. 1. The email address entered above will receive email message with the following subject line: `AWS Notification - Subscription Confirmation`. Follow the directions to confirm your subscription. **To create the EventBridge rule** 1. Open the Amazon EventBridge console at [https://console.aws.amazon.com/events/](https://console.aws.amazon.com/events/). 1. In the navigation pane, choose **Rules**, and then choose **Create rule**. 1. For **Name**, enter a name for the new rule. 1. For **Rule type**, choose **Rule with an event pattern**. 1. Choose **Next**. 1. In the **Event pattern**, do the following: 1. For **Event source**, choose **AWS services**. 1. For **AWS service**, choose **AWS Health**. 1. For **Event type**, choose **EC2 ODCR Underutilization Notification**. 1. Choose **Next**. 1. For **Target 1**, do the following: 1. For **Target types**, choose **AWS service**. 1. For **Select a target**, choose **SNS topic**. 1. For **Topic**, choose the topic that you created earlier. 1. Choose **Next** and then **Next** again. 1. Choose **Create rule**. ## Email and AWS Health Dashboard notifications AWS Health sends the following email and Health Dashboard notifications when capacity utilization for Capacity Reservations in your account drops below 20 percent. + Individual notifications for each newly created Capacity Reservation that has been below 20 percent utilization over the last 24-hour period. + A summary notification for all Capacity Reservations that have been below 20 percent utilization over the last 7-day period. The email notifications and Health Dashboard notifications are sent to the email address associated with the AWS account that owns the Capacity Reservations. The notifications include the following information: + The ID of the Capacity Reservation. + The Availability Zone of the Capacity Reservation. + The average utilization rate for the Capacity Reservation. + The instance type and platform (operating system) of the Capacity Reservation. Additionally, when capacity utilization for a Capacity Reservation in your account drops below 20 percent over a 24-hour and 7-day period, AWS Health sends events to EventBridge. With EventBridge, you can create rules that activate automatic actions, such as sending email notifications or triggering AWS Lambda functions, in response to such events. For more information, see [Monitor Capacity Reservation underutilization](#cr-eventbridge). # Monitor state changes for future-dated Capacity Reservations Monitor state changes Amazon EC2 sends an event to Amazon EventBridge when the state of a future-dated Capacity Reservation changes. The following is example of this event. In this example, the future-dated Capacity Reservation entered the `scheduled` state. Note the state highlighted in the `detail-type` field. ``` { "version":"0", "id":"12345678-1234-1234-1234-123456789012", "detail-type":"EC2 Capacity Reservation Scheduled", "source":"aws.ec2", "account":"123456789012", "time":"yyyy-mm-ddThh:mm:ssZ", "region":"us-east-1", "resources":[ "arn:aws:ec2:us-east-1:123456789012:capacity-reservation/cr-1234567890abcdefg" ], "detail":{ "capacity-reservation-id":"cr-1234567890abcdefg", "state":"scheduled" } } ``` The possible values for the `detail-type` field are: + `Scheduled` + `Active` + `Delayed` + `Unsupported` + `Failed` + `Expired` For more information about these states, see [View the state of a Capacity Reservation](capacity-reservations-view.md). You can create Amazon EventBridge events that monitor for these events and then trigger specific actions when they occur. For more information, see [Creating rules that react to events in Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-create-rule.html). To create a rule that monitors for all state change events, you can use the following event pattern. ``` { "source": ["aws.ec2"], "detail-type": [{ "prefix": "EC2 Capacity Reservation" }] } ``` To create a rule that monitors for only specific state changes, you can use the following event pattern. ``` { "source": ["aws.ec2"], "detail-type": [{ "prefix": "EC2 Capacity Reservation state" }] } ``` For example, the following event pattern monitors for events that are sent when a future-dated Capacity Reservation enters the `active` state. ``` { "source": ["aws.ec2"], "detail-type": [{ "prefix": "EC2 Capacity Reservation Active" }] } ``` # Interruptible Capacity Reservations Interruptible Capacity Reservations help you make unused capacity temporarily available for other workloads within your account. This gives you control to reclaim capacity when needed. When you reclaim capacity, any instances running inside the interruptible reservation are terminated. After creating an interruptible reservation, you can share it with additional AWS accounts or your AWS organization using AWS Resource Access Manager (RAM). Use interruptible Capacity Reservations when you have unused reserved capacity during off-peak periods, between deployments, or when workloads scale down. If you know another team that could use this capacity, you can make it available by creating an interruptible Capacity Reservation. When your critical workload needs capacity back, you can reclaim it. You can use interruptible Capacity Reservations as one of the following: + **Capacity owner** – You own the source Capacity Reservation and create the interruptible Capacity Reservation to share unused capacity with other teams while retaining control to reclaim it when needed. + **Capacity consumer** – You launch instances into shared interruptible reservations, understanding that your instances may be terminated when the owner reclaims capacity. **Topics** + [ ## How it works ](#how-interruptible-cr-works) + [ ## Billing ](#interruptible-cr-billing) + [ ## Considerations ](#interruptible-cr-considerations) + [ # Interruptible Capacity Reservations for capacity owners ](capacity-owner-procedures.md) + [ # Interruptible Capacity Reservations for capacity consumers ](capacity-consumer-procedures.md) + [ # Monitor interruptible Capacity Reservations with EventBridge and CloudTrail ](monitor-interruptible-cr.md) ## How it works To make unused capacity available to other teams, create an interruptible reservation by specifying the number of unused instances you want to share from your source reservation. When you create the interruptible reservation, we transfer these instances from your source reservation to the new interruptible reservation within your account. We retain the association between the source reservation and the interruptible Capacity Reservation. As a result, when you reclaim your capacity, any running consumer instances are terminated, and the capacity is restored to your original source reservation. Key features: + Make unused capacity temporarily available while maintaining control to reclaim it + Reclaim capacity at any time. For more information, see [Reclamation process and tracking](capacity-owner-procedures.md#reclamation-process) + Share with additional accounts or your AWS organization using AWS Resource Access Manager (RAM) ## Billing When you create an interruptible reservation, you're billed for it as an independent new reservation. This splits your billing: + Source reservation: You're billed for total capacity minus allocated capacity + Interruptible reservation: You're billed for the allocated capacity For more information about On-Demand Capacity Reservation billing, see [Capacity Reservation pricing and billing](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-reservations-pricing-billing.html). ## Considerations Before using interruptible Capacity Reservations, review the following limitations and requirements that apply to capacity owners and consumers. ### Capacity owners + You cannot directly modify or cancel an interruptible Capacity Reservation. To edit it, update the capacity allocated from the source Capacity Reservation. + You can only view, launch, tag, share, and assign billing for interruptible reservations. + You can create only one interruptible allocation per source Capacity Reservation. ### Capacity consumers + Interruptible Capacity Reservations are by default targeted Capacity Reservations, so you need to target them in your instance launch. + You can't add interruptible Capacity Reservations to capacity reservation groups. + We recommend that you only use interruptible Capacity Reservations for applications that can be interrupted. + Your instances will be terminated when the owner reclaims capacity - there is no fallback to On-Demand or Spot. For more information, see [Interruption experience](capacity-consumer-procedures.md#interruption-experience). # Interruptible Capacity Reservations for capacity owners Capacity owners The capacity owner is the account that owns the source Capacity Reservation and creates the interruptible Capacity Reservation to share unused capacity with other teams while retaining control to reclaim it when needed. This section covers how you (the capacity owner) can create, modify, reclaim, and track an interruptible Capacity Reservation. **Topics** + [ ## Creating an interruptible Capacity Reservation ](#creating-interruptible-cr) + [ ## View your interruptible Capacity Reservation ](#view-interruptible-cr) + [ ## Modifying your interruptible Capacity Reservation ](#modify-interruptible-cr) + [ ## Reclamation process and tracking ](#reclamation-process) + [ ## Sharing interruptible reservations ](#sharing-interruptible-reservations) ## Creating an interruptible Capacity Reservation Create an interruptible Capacity Reservation to make unused capacity from your source reservation available for other workloads while maintaining control to reclaim it when needed. ### Prerequisites Before creating an interruptible allocation, ensure your source On-Demand Capacity Reservation meets these requirements: + Your Capacity Reservation must be in active state with no end date set. You can't create allocations from reservations that are pending, expired, cancelled, or have scheduled end dates. + Your Capacity Reservation must have available capacity for allocation. You can only allocate available instances (also called unused capacity). + You can create only one interruptible allocation per source Capacity Reservation. If an allocation already exists, you must modify or cancel it before creating a new one. + You can allocate a maximum of 1000 instances at once to an interruptible Capacity Reservation. Use can use the console or the AWS CLI to create an interruptible Capacity Reservation. ------ #### [ Console ] **To create an interruptible Capacity Reservation** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. Choose **Capacity Reservations**. 1. Select your Capacity Reservation. 1. Choose **Actions**, **Create interruptible allocation**. 1. For **Instances to allocate**, enter the number of instances to allocate. 1. (Optional) Add tags. 1. Choose **Create interruptible capacity allocation**. ------ #### [ AWS CLI ] **To create an interruptible Capacity Reservation** Use the [create-interruptible-capacity-reservation-allocation](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/create-interruptible-capacity-reservation-allocation.html) command: ``` aws ec2 create-interruptible-capacity-reservation-allocation \ --capacity-reservation-id cr-1234567890abcdef0 \ --instance-count 10 ``` ------ ## View your interruptible Capacity Reservation After creating an interruptible Capacity Reservation, you can view the interruptible reservation in your account or from a specific resource. ### View all interruptible Capacity Reservations in your account Use the following procedure to view the interruptible Capacity Reservations in your account. ------ #### [ Console ] **To view the interruptible Capacity Reservations in your account** 1. Go to the Capacity Reservations page in the console. 1. Look for reservations with **Interruptible** in the type column. 1. Select the interruptible reservation to view details. ------ #### [ AWS CLI ] **To view the interruptible Capacity Reservations in your account** ``` aws ec2 describe-capacity-reservations \ --capacity-reservation-id cr-interruptible-id \ --filters Name=interruptible,Values=true ``` ------ ### View interruptible Capacity Reservation from a specific source Use the following procedure to view the interruptible Capacity Reservation created from a specific source Capacity Reservation. ``` aws ec2 describe-capacity-reservations \ --capacity-reservation-id cr-source-id ``` In the response, you'll find an `interruptibleCapacityAllocations` object that contains the interruptible Capacity Reservation ID and allocation details. For information about the response structure, see [InterruptibleCapacityAllocation](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_InterruptibleCapacityAllocation.html) in the *Amazon EC2 API Reference*. ## Modifying your interruptible Capacity Reservation Use the following procedures to edit or cancel your interruptible Capacity Reservation. **Note** When you reduce the allocation, we first reclaim available instances, then running instances, until we meet the requested count. If we can meet the count entirely with available instances, no termination occurs. All modifications to allocated instance count are done through the source Capacity Reservation, not directly on the interruptible Capacity Reservation. You can only modify an interruptible Capacity Reservation by a maximum of 1000 instances at once (increase or decrease). ### Edit your interruptible Capacity Reservation Use the following procedure to edit your interruptible Capacity Reservation. ------ #### [ Console ] 1. From the source Capacity Reservation details page, choose **Actions**. Then, **Edit interruptible Capacity Reservation**. 1. For **Instances to allocate**, enter the new number: + Add more capacity to share + Reclaim capacity to your source Capacity Reservation 1. Choose **Update**. ------ #### [ AWS CLI ] ``` aws ec2 update-interruptible-capacity-reservation-allocation \ --capacity-reservation-id cr-1234567890abcdef0 \ --target-instance-count 80 ``` ------ ### Cancel your interruptible Capacity Reservation Use the following procedure to permanently remove the allocation and return all capacity. ------ #### [ Console ] 1. From the source Capacity Reservation details page, navigate to the interruptible capacity allocation details. 1. Choose **Edit interruptible allocation**. 1. For Instance count, enter **0**. 1. Choose **Update**. ------ #### [ AWS CLI ] ``` aws ec2 update-interruptible-capacity-reservation-allocation \ --capacity-reservation-id cr-1234567890abcdef0 \ --target-instance-count 0 ``` ------ ## Reclamation process and tracking When you reclaim capacity: + Running instances receive a 2-minute interruption warning through EventBridge events. + After the notice period, running instances in the reclaimed capacity enter a shutting down state and get terminated. + When terminated, the reclaimed instances become available in your source Capacity Reservation for immediate use. + Your allocation status changes from **updating** to **active** when complete. Complete reclamation can take a few minutes depending on instance type and shutdown time. For more information about the EventBridge notification you receive when the process is complete, see [Reclamation completion](monitor-interruptible-cr.md#reclamation-completion). ### Track reclamation status Monitor reclamation progress by describing your source reservation: ``` aws ec2 describe-capacity-reservations \ --capacity-reservation-id cr-1234567890abcdef0 ``` The response shows these fields within the `interruptibleCapacityAllocation` object: + `instance-count`: Current allocated instances + `target-instance-count`: Requested quantity after reclamation + `status`: **updating** during reclamation and **active** when complete ## Sharing interruptible reservations You can share interruptible reservations only within your AWS organization using AWS Resource Access Manager (RAM). Considerations: + If a consumer account leaves your organization, the interruptible reservation is automatically unshared from that account. + Any instances running in the unshared reservation are eventually terminated. + All other sharing functionality works the same as standard Capacity Reservations. For complete sharing procedures, see [Sharing Capacity Reservations](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-reservation-sharing.html). # Interruptible Capacity Reservations for capacity consumers Capacity consumers The capacity consumer is the account that launches instances into shared interruptible Capacity Reservations, understanding that their instances may be terminated when the owner reclaims capacity. This section covers how you (the capacity consumer) can launch instances into an interruptible Capacity Reservation and learn about what happens when capacity is reclaimed by the owner. **Topics** + [ ## View an interruptible Capacity Reservation ](#view-interruptible-cr-consumer) + [ ## Launch instances into interruptible reservations ](#launch-instances-interruptible) + [ ## Interruption experience ](#interruption-experience) ## View an interruptible Capacity Reservation Use the following procedures to view an interruptible Capacity Reservation. ------ #### [ Console ] **To view interruptible Capacity Reservations in your account** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. Choose **Capacity Reservations**. 1. In the **Type** column, look for reservations marked as **Interruptible**. 1. Note the reservation IDs for use in your instance launches. ------ #### [ AWS CLI ] **To find all interruptible Capacity Reservations in your account** Use the [describe-capacity-reservations](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-capacity-reservations.html) command: ``` aws ec2 describe-capacity-reservations \ --filters Name=state,Values=active ``` Look for reservations where `Interruptible` is set to `true` in the response. **To filter specifically for interruptible reservations** Use the following command: ``` aws ec2 describe-capacity-reservations \ --capacity-reservation-ids cr-example123 \ --query 'CapacityReservations[?Interruptible==`true`]' ``` ------ **Note** Interruptible Capacity Reservations are by default targeted Capacity Reservations, so you need to target them specifically in your instance launch. Unlike open reservations, interruptible reservations will not automatically cover matching instances. You must explicitly specify the reservation ID when launching. ## Launch instances into interruptible reservations Use the following procedure to launch Amazon EC2 instances into interruptible Capacity Reservations within your account. **Note** We recommend that you only use interruptible Capacity Reservations for applications that can be interrupted. ------ #### [ Console ] **To launch instances into interruptible Capacity Reservations** 1. Open the Amazon Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. From the Amazon EC2 dashboard, choose **Launch instance**. 1. Configure your instance settings. 1. In **Advanced details** for Capacity Reservation, choose **Launch interruptible instances in your active reservation**. 1. Select the interruptible reservation ID and the new instance purchasing option. 1. Choose **Launch instance**. ------ #### [ AWS CLI ] ``` aws ec2 run-instances \ --instance-type m5.large \ --count 2 \ --image-id ami-12345678 \ --instance-market-options '{ "MarketType": "interruptible-capacity-reservation" }' \ --capacity-reservation-specification '{ "CapacityReservationTarget": { "CapacityReservationId": "cr-abcdef1234567890" } }' ``` ------ ### Launch instances with Auto Scaling Groups You can also launch instances into interruptible reservations using Auto Scaling Groups with launch templates. Configure the launch template with the interruptible market type and reservation ID, then create your Auto Scaling Group using that template. For more information, see [Interruptible Capacity Reservations with EC2 Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-interruptible-capacity-reservations.html). ## Interruption experience When capacity is reclaimed by the owner, you receive an interruption notice 2 minutes before instance termination. This warning comes through EventBridge events, giving you time to: + Save your work or checkpoint your applications + Shut down processes + Prepare for instance termination The EventBridge event includes details about which instances will be terminated and the exact termination time. For more information, see [Instance interruption warning](monitor-interruptible-cr.md#instance-interruption-warning). # Monitor interruptible Capacity Reservations with EventBridge and CloudTrail Monitor with EventBridge and CloudTrail Interruptible Capacity Reservations send EventBridge notifications and CloudTrail events to help you monitor and respond to capacity changes. **Topics** + [ ## EventBridge notifications ](#eventbridge-notifications) + [ ## CloudTrail events ](#cloudtrail-events) ## EventBridge notifications You receive two types of EventBridge notifications. For information about how to set up EventBridge notifications, see [Creating Amazon EventBridge rules](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-create-rule.html). ### Instance interruption warning If you're running instances in an interruptible reservation, you receive this notification 2 minutes before your instances are terminated: ``` { "version": "0", "id": "12345678-1234-1234-1234-123456789012", "detail-type": "EC2 Capacity Reservation Instance Interruption Warning", "source": "aws.ec2", "account": "[instance owner Account ID]", "time": "[Current time in yyyy-mm-ddThh:mm:ssZ]", "resources": "[instance arn]", "region": "[region]", "detail": { "instance-id": "[instance-id]", "instance-action": "terminate", "instance-termination-time": "yyyy-mm-ddThh:mm:ssZ", "azId": "[availability-zone-id]" } } ``` ### Reclamation completion If you own the source reservation, you receive this notification when capacity reclamation finishes: ``` { "version": "0", "id": "12345678-1234-1234-1234-123456789012", "detail-type": "EC2 Interruptible Capacity Reservation Allocation Reclamation Completed", "source": "aws.ec2", "account": "[source Capacity Reservation Owner Account ID]", "time": "[Current time in yyyy-mm-ddThh:mm:ssZ]", "region": "us-east-1", "resources": ["source_cr_arn"], "detail": { "sourceCapacityReservationId": "string", "instanceType": "string", "availabilityZoneId": "string", "TotalInstanceCount": "current total count in the source", "ReclaimedInstanceCount": "count of instances added to the source", "targetInstanceCount": "number" } } ``` ## CloudTrail events CloudTrail logs these events for interruptible Capacity Reservations: + `InterruptibleCapacityReservationCreated` — When you create an interruptible allocation + `InterruptibleCapacityReservationAllocationUpdated` — When you modify the allocation + `InterruptibleCapacityReservationCancelled` — When you cancel the allocation + `CapacityReservationModified` — When we modify the source reservation for allocation + `InterruptibleCapacityReservationInstancesTerminated` — When we terminate instances during reclamation