# 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 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 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 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 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 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 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.