# Reserved Instances for Amazon EC2 overview Reserved Instances **Important** We recommend Savings Plans over Reserved Instances. Saving Plans are the easiest and most flexible way to save money on your AWS compute costs and offer lower prices (up to 72% off On-Demand pricing), just like Reserved Instances. However, Savings Plans are different to Reserved Instances. With Reserved Instances, you make a commitment to a specific instance configuration, whereas with Savings Plans, you have the flexibility to use the instance configurations that best meet your needs. To use Savings Plans, you make a commitment to a consistent usage amount, measured in USD per hour. For more information, see the [AWS Savings Plans User Guide](https://docs.aws.amazon.com/savingsplans/latest/userguide/). Reserved Instances provide you with significant savings on your Amazon EC2 costs compared to On-Demand Instance pricing. Reserved Instances are not physical instances, but rather a billing discount applied to the use of On-Demand Instances in your account. These On-Demand Instances must match certain attributes, such as instance type and Region, in order to benefit from the billing discount. **Topics** + [ ## Reserved Instance example scenario ](#ri-example-scenario) + [ ## Key variables that determine Reserved Instance pricing ](#ri-key-pricing-variables) + [ # Regional and zonal Reserved Instances (scope) ](reserved-instances-scope.md) + [ # Types of Reserved Instances (offering classes) ](reserved-instances-types.md) + [ # How Reserved Instance discounts are applied ](apply_ri.md) + [ # Use your Reserved Instances ](using-reserved-instances.md) + [ # How billing works with Reserved Instances ](concepts-reserved-instances-application.md) + [ # Buy Reserved Instances for Amazon EC2 ](ri-market-concepts-buying.md) + [ # Sell Reserved Instances for Amazon EC2 in the Reserved Instance Marketplace ](ri-market-general.md) + [ # Modify Reserved Instances ](ri-modifying.md) + [ # Exchange Convertible Reserved Instances ](ri-convertible-exchange.md) + [ # Reserved Instance quotas ](ri-limits.md) ## Reserved Instance example scenario The following diagram shows a basic scenario of purchasing and using Reserved Instances. ![\[Purchasing Reserved Instances.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-basics.png) In this scenario, you have a running On-Demand Instance (T2) in your account, for which you're currently paying On-Demand rates. You purchase a Reserved Instance that matches the attributes of your running instance, and the billing benefit is immediately applied. Next, you purchase a Reserved Instance for a C4 instance. You do not have any running instances in your account that match the attributes of this Reserved Instance. In the final step, you launch an instance that matches the attributes of the C4 Reserved Instance, and the billing benefit is immediately applied. ## Key variables that determine Reserved Instance pricing The Reserved Instance pricing is determined by the following key variables. ### Instance attributes A Reserved Instance has four instance attributes that determine its price. + **Instance type**: For example, `m4.large`. This is composed of the instance family (for example, `m4`) and the instance size (for example, `large`). + **Region**: The Region in which the Reserved Instance is purchased. + **Tenancy**: Whether your instance runs on shared (default) or single-tenant (dedicated) hardware. For more information, see [Amazon EC2 Dedicated Instances](dedicated-instance.md). + **Platform**: The operating system; for example, Windows or Linux/Unix. For more information, see [Choosing a platform](ri-market-concepts-buying.md#ri-choosing-platform). ### Term commitment You can purchase a Reserved Instance for a one-year or three-year commitment, with the three-year commitment offering a bigger discount. + **One-year**: A year is defined as 31536000 seconds (365 days). + **Three-year**: Three years is defined as 94608000 seconds (1095 days). Reserved Instances do not renew automatically; when they expire, you can continue using the EC2 instance without interruption, but you are charged On-Demand rates. In the above example, when the Reserved Instances that cover the T2 and C4 instances expire, you go back to paying the On-Demand rates until you terminate the instances or purchase new Reserved Instances that match the instance attributes. **Important** After you purchase a Reserved Instance, you cannot cancel your purchase. However, you might be able to [modify](ri-modifying.md), [exchange](ri-convertible-exchange.md), or [sell](ri-market-general.md) your Reserved Instance if your needs change. ### Payment options The following payment options are available for Reserved Instances: + **All Upfront**: Full payment is made at the start of the term, with no other costs or additional hourly charges incurred for the remainder of the term, regardless of hours used. + **Partial Upfront**: A portion of the cost must be paid upfront and the remaining hours in the term are billed at a discounted hourly rate, regardless of whether the Reserved Instance is being used. + **No Upfront**: You are billed a discounted hourly rate for every hour within the term, regardless of whether the Reserved Instance is being used. No upfront payment is required. **Note** No Upfront Reserved Instances are based on a contractual obligation to pay monthly for the entire term of the reservation. For this reason, a successful billing history is required before you can purchase No Upfront Reserved Instances. Generally speaking, you can save more money making a higher upfront payment for Reserved Instances. You can also find Reserved Instances offered by third-party sellers at lower prices and shorter term lengths on the Reserved Instance Marketplace. For more information, see [Sell Reserved Instances for Amazon EC2 in the Reserved Instance Marketplace](ri-market-general.md). ### Offering class If your computing needs change, you might be able to modify or exchange your Reserved Instance, depending on the offering class. + **Standard**: These provide the most significant discount, but can only be modified. Standard Reserved Instances can't be exchanged. + **Convertible**: These provide a lower discount than Standard Reserved Instances, but can be exchanged for another Convertible Reserved Instance with different instance attributes. Convertible Reserved Instances can also be modified. For more information, see [Types of Reserved Instances (offering classes)](reserved-instances-types.md). **Important** After you purchase a Reserved Instance, you cannot cancel your purchase. However, you might be able to [modify](ri-modifying.md), [exchange](ri-convertible-exchange.md), or [sell](ri-market-general.md) your Reserved Instance if your needs change. For more information, see the [Amazon EC2 Reserved Instances Pricing page](https://aws.amazon.com/ec2/pricing/reserved-instances/pricing/). # Regional and zonal Reserved Instances (scope) When you purchase a Reserved Instance, you determine the scope of the Reserved Instance. The scope is either regional or zonal. + **Regional**: When you purchase a Reserved Instance for a Region, it's referred to as a *regional* Reserved Instance. + **Zonal**: When you purchase a Reserved Instance for a specific Availability Zone, it's referred to as a *zonal* Reserved Instance. The scope does not affect the price. You pay the same price for a regional or zonal Reserved Instance. For more information about Reserved Instance pricing, see [Key variables that determine Reserved Instance pricing](ec2-reserved-instances.md#ri-key-pricing-variables) and [Amazon EC2 Reserved Instances Pricing](https://aws.amazon.com/ec2/pricing/reserved-instances/pricing/). For more information about how to specify the scope of a Reserved Instance, see [RI Attributes](https://aws.amazon.com/ec2/pricing/reserved-instances/#riattributes), specifically the **Availability Zone** bullet. ## Differences between regional and zonal Reserved Instances The following table highlights some key differences between regional Reserved Instances and zonal Reserved Instances: | | Regional Reserved Instances | Zonal Reserved Instances | | --- | --- | --- | | Ability to reserve capacity | A regional Reserved Instance does *not* reserve capacity. | A zonal Reserved Instance reserves capacity in the specified Availability Zone. | | Availability Zone flexibility | The Reserved Instance discount applies to instance usage in any Availability Zone in the specified Region. | No Availability Zone flexibility—the Reserved Instance discount applies to instance usage in the specified Availability Zone only. | | Instance size flexibility | The Reserved Instance discount applies to instance usage within the instance family, regardless of size. Only supported on Amazon Linux/Unix Reserved Instances with default tenancy. For more information, see [Instance size flexibility determined by normalization factor](apply_ri.md#ri-normalization-factor). | No instance size flexibility—the Reserved Instance discount applies to instance usage for the specified instance type and size only. | | Queuing a purchase | You can queue purchases for regional Reserved Instances. | You can't queue purchases for zonal Reserved Instances. | For more information and examples, see [How Reserved Instance discounts are applied](apply_ri.md). # Types of Reserved Instances (offering classes) The offering class of a Reserved Instance is either Standard or Convertible. A Standard Reserved Instance provides a more significant discount than a Convertible Reserved Instance, but you can't exchange a Standard Reserved Instance. You can exchange Convertible Reserved Instances. You can modify Standard and Convertible Reserved Instances. The configuration of a Reserved Instance comprises a single instance type, platform, scope, and tenancy over a term. If your computing needs change, you might be able to modify or exchange your Reserved Instance. ## Differences between Standard and Convertible Reserved Instances The following are the differences between Standard and Convertible Reserved Instances. | | Standard Reserved Instance | Convertible Reserved Instance | | --- | --- | --- | | Modify Reserved Instances | Some attributes can be modified. For more information, see [Modify Reserved Instances](ri-modifying.md). | Some attributes can be modified. For more information, see [Modify Reserved Instances](ri-modifying.md). | | Exchange Reserved Instances | Can't be exchanged. | Can be exchanged during the term for another Convertible Reserved Instance with new attributes, including instance family, instance type, platform, scope, or tenancy. For more information, see [Exchange Convertible Reserved Instances](ri-convertible-exchange.md). | | Sell in the Reserved Instance Marketplace | Can be sold in the Reserved Instance Marketplace. | Can't be sold in the Reserved Instance Marketplace. | | Buy in the Reserved Instance Marketplace | Can be bought in the Reserved Instance Marketplace. | Can't be bought in the Reserved Instance Marketplace. | # How Reserved Instance discounts are applied Reserved Instances are not physical instances, but rather a billing discount that is applied to the running On-Demand Instances in your account. The On-Demand Instances must match certain specifications of the Reserved Instances in order to benefit from the billing discount. If you purchase a Reserved Instance and you already have a running On-Demand Instance that matches the specifications of the Reserved Instance, the billing discount is applied immediately and automatically. You do not have to restart your instances. If you do not have an eligible running On-Demand Instance, launch an On-Demand Instance with the same specifications as your Reserved Instance. For more information, see [Use your Reserved Instances](using-reserved-instances.md). The offering class (Standard or Convertible) of the Reserved Instance does not affect how the billing discount is applied. **Topics** + [ ## How zonal Reserved Instances are applied ](#apply-zonal-ri) + [ ## How regional Reserved Instances are applied ](#apply-regional-ri) + [ ## Instance size flexibility ](#ri-instance-size-flexibility) + [ ## Examples of applying Reserved Instances ](#ri-usage-examples) ## How zonal Reserved Instances are applied A Reserved Instance that is purchased to reserve capacity in a specific Availability Zone is called a zonal Reserved Instance. + The Reserved Instance discount applies to matching instance usage in that Availability Zone. + The attributes (tenancy, platform, Availability Zone, instance type, and instance size) of the running instances must match that of the Reserved Instances. For example, if you purchase two `c4.xlarge` default tenancy Linux/Unix Standard Reserved Instances for Availability Zone us-east-1a, then up to two `c4.xlarge` default tenancy Linux/Unix instances running in the Availability Zone us-east-1a can benefit from the Reserved Instance discount. ## How regional Reserved Instances are applied A Reserved Instance that is purchased for a Region is called a regional Reserved Instance, and provides Availability Zone and instance size flexibility. + The Reserved Instance discount applies to instance usage in any Availability Zone in that Region. + The Reserved Instance discount applies to instance usage within the instance family, regardless of size—this is known as [instance size flexibility](#ri-instance-size-flexibility). ## Instance size flexibility With instance size flexibility, the Reserved Instance discount applies to instance usage for instances that have the same [ family](https://docs.aws.amazon.com/ec2/latest/instancetypes/instance-type-names.html). The Reserved Instance is applied from the smallest to the largest instance size within the instance family based on the normalization factor. For an example of how the Reserved Instance discount is applied, see [Scenario 2: Reserved Instances in a single account using the normalization factor](#ri-usage-ex2). ### Limitations + **Supported: **Instance size flexibility is only supported for Regional Reserved Instances. + **Not supported:** Instance size flexibility is *not supported* for the following Reserved Instances: + Reserved Instances that are purchased for a specific Availability Zone (zonal Reserved Instances) + Reserved Instances for G4ad, G4dn, G5, G5g, G6, G6e, G6f, Gr6, Gr6f, hpc7a, P5, Inf1, Inf2, u7i-6tb, and u7i-8tb instances + Reserved Instances for Windows Server, Windows Server with SQL Standard, Windows Server with SQL Server Enterprise, Windows Server with SQL Server Web, RHEL, and SUSE Linux Enterprise Server + Reserved Instances with dedicated tenancy ### Instance size flexibility determined by normalization factor Instance size flexibility is determined by the normalization factor of the instance size. The discount applies either fully or partially to running instances of the same instance family, depending on the instance size of the reservation, in any Availability Zone in the Region. The only attributes that must be matched are the instance family, tenancy, and platform. The following table lists the different sizes within an instance family, and the corresponding normalization factor. This scale is used to apply the discounted rate of Reserved Instances to the normalized usage of the instance family. | Instance size | Normalization factor | | --- | --- | | nano | 0.25 | | micro | 0.5 | | small | 1 | | medium | 2 | | large | 4 | | xlarge | 8 | | 2xlarge | 16 | | 3xlarge | 24 | | 4xlarge | 32 | | 6xlarge | 48 | | 8xlarge | 64 | | 9xlarge | 72 | | 10xlarge | 80 | | 12xlarge | 96 | | 16xlarge | 128 | | 18xlarge | 144 | | 24xlarge | 192 | | 32xlarge | 256 | | 48xlarge | 384 | | 56xlarge | 448 | | 112xlarge | 896 | For example, a `t2.medium` instance has a normalization factor of 2. If you purchase a `t2.medium` default tenancy Amazon Linux/Unix Reserved Instance in the US East (N. Virginia) and you have two running `t2.small` instances in your account in that Region, the billing benefit is applied in full to both instances. ![\[Applying a Regional Reserved Instance.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-instance-flex-full.png) Or, if you have one `t2.large` instance running in your account in the US East (N. Virginia) Region, the billing benefit is applied to 50% of the usage of the instance. ![\[Applying a Regional Reserved Instance.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-instance-flex-partial.png) The normalization factor is also applied when modifying Reserved Instances. For more information, see [Modify Reserved Instances](ri-modifying.md). #### Normalization factor for bare metal instances Instance size flexibility also applies to bare metal instances within the instance family. If you have regional Amazon Linux/Unix Reserved Instances with shared tenancy on bare metal instances, you can benefit from the Reserved Instance savings within the same instance family. The opposite is also true: if you have regional Amazon Linux/Unix Reserved Instances with shared tenancy on instances in the same family as a bare metal instance, you can benefit from the Reserved Instance savings on the bare metal instance. The `metal` instance size does not have a single normalization factor. A bare metal instance has the same normalization factor as the equivalent virtualized instance size within the same instance family. For example, an `i3.metal` instance has the same normalization factor as an `i3.16xlarge` instance. | Instance size | Normalization factor | | --- | --- | | a1.metal | 32 | | m5zn.metal \$1 x2iezn.metal z1d.metal | 96 | | c6g.metal \$1 c6gd.metal \$1 i3.metal \$1 m6g.metal \$1 m6gd.metal \$1 r6g.metal \$1 r6gd.metal \$1 x2gd.metal | 128 | | c5n.metal | 144 | | c5.metal \$1 c5d.metal \$1 i3en.metal \$1 m5.metal \$1 m5d.metal \$1 m5dn.metal \$1 m5n.metal \$1 r5.metal \$1 r5b.metal \$1 r5d.metal \$1 r5dn.metal \$1 r5n.metal | 192 | | c6i.metal \$1 c6id.metal \$1 m6i.metal \$1 m6id.metal \$1 r6d.metal \$1 r6id.metal | 256 | | u-18tb1.metal \$1 u-24tb1.metal | 448 | | u-6tb1.metal \$1 u-9tb1.metal \$1 u-12tb1.metal | 896 | For example, an `i3.metal` instance has a normalization factor of 128. If you purchase an `i3.metal` default tenancy Amazon Linux/Unix Reserved Instance in the US East (N. Virginia), the billing benefit can apply as follows: + If you have one running `i3.16xlarge` in your account in that Region, the billing benefit is applied in full to the `i3.16xlarge` instance (`i3.16xlarge` normalization factor = 128). + Or, if you have two running `i3.8xlarge` instances in your account in that Region, the billing benefit is applied in full to both `i3.8xlarge` instances (`i3.8xlarge` normalization factor = 64). + Or, if you have four running `i3.4xlarge` instances in your account in that Region, the billing benefit is applied in full to all four `i3.4xlarge` instances (`i3.4xlarge` normalization factor = 32). The opposite is also true. For example, if you purchase two `i3.8xlarge` default tenancy Amazon Linux/Unix Reserved Instances in the US East (N. Virginia), and you have one running `i3.metal` instance in that Region, the billing benefit is applied in full to the `i3.metal` instance. ## Examples of applying Reserved Instances **Topics** + [ ### Scenario 1: Reserved Instances in a single account ](#ri-usage-ex1) + [ ### Scenario 2: Reserved Instances in a single account using the normalization factor ](#ri-usage-ex2) + [ ### Scenario 3: Regional Reserved Instances in linked accounts ](#ri-usage-ex3) + [ ### Scenario 4: Zonal Reserved Instances in a linked account ](#ri-usage-ex4) ### Scenario 1: Reserved Instances in a single account You are running the following On-Demand Instances in account A: + 4 x `m3.large` Linux, default tenancy instances in Availability Zone us-east-1a + 2 x `m4.xlarge` Amazon Linux, default tenancy instances in Availability Zone us-east-1b + 1 x `c4.xlarge` Amazon Linux, default tenancy instances in Availability Zone us-east-1c You purchase the following Reserved Instances in account A: + 4 x `m3.large` Linux, default tenancy Reserved Instances in Availability Zone us-east-1a (capacity is reserved) + 4 x `m4.large` Amazon Linux, default tenancy Reserved Instances in Region us-east-1 + 1 x `c4.large` Amazon Linux, default tenancy Reserved Instances in Region us-east-1 The Reserved Instance benefits are applied in the following way: + The discount and capacity reservation of the four `m3.large` zonal Reserved Instances is used by the four `m3.large` instances because the attributes (instance size, Region, platform, tenancy) between them match. + The `m4.large` regional Reserved Instances provide Availability Zone and instance size flexibility, because they are regional Amazon Linux Reserved Instances with default tenancy. An `m4.large` is equivalent to 4 normalized units/hour. You've purchased four `m4.large` regional Reserved Instances, and in total, they are equal to 16 normalized units/hour (4x4). Account A has two `m4.xlarge` instances running, which is equivalent to 16 normalized units/hour (2x8). In this case, the four `m4.large` regional Reserved Instances provide the full billing benefit to the usage of the two `m4.xlarge` instances. + The `c4.large` regional Reserved Instance in us-east-1 provides Availability Zone and instance size flexibility, because it is a regional Amazon Linux Reserved Instance with default tenancy, and applies to the `c4.xlarge` instance. A `c4.large` instance is equivalent to 4 normalized units/hour and a `c4.xlarge` is equivalent to 8 normalized units/hour. In this case, the `c4.large` regional Reserved Instance provides partial benefit to `c4.xlarge` usage. This is because the `c4.large` Reserved Instance is equivalent to 4 normalized units/hour of usage, but the `c4.xlarge` instance requires 8 normalized units/hour. Therefore, the `c4.large` Reserved Instance billing discount applies to 50% of `c4.xlarge` usage. The remaining `c4.xlarge` usage is charged at the On-Demand rate. ### Scenario 2: Reserved Instances in a single account using the normalization factor You are running the following On-Demand Instances in account A: + 2 x `m3.xlarge` Amazon Linux, default tenancy instances in Availability Zone us-east-1a + 2 x `m3.large` Amazon Linux, default tenancy instances in Availability Zone us-east-1b You purchase the following Reserved Instance in account A: + 1 x `m3.2xlarge` Amazon Linux, default tenancy Reserved Instance in Region us-east-1 The Reserved Instance benefits are applied in the following way: + The `m3.2xlarge` regional Reserved Instance in us-east-1 provides Availability Zone and instance size flexibility, because it is a regional Amazon Linux Reserved Instance with default tenancy. It applies first to the `m3.large` instances and then to the `m3.xlarge` instances, because it applies from the smallest to the largest instance size within the instance family based on the normalization factor. An `m3.large` instance is equivalent to 4 normalized units/hour. An `m3.xlarge` instance is equivalent to 8 normalized units/hour. An `m3.2xlarge` instance is equivalent to 16 normalized units/hour. The benefit is applied as follows: The `m3.2xlarge` regional Reserved Instance provides full benefit to 2 x `m3.large` usage, because together these instances account for 8 normalized units/hour. This leaves 8 normalized units/hour to apply to the `m3.xlarge` instances. With the remaining 8 normalized units/hour, the `m3.2xlarge` regional Reserved Instance provides full benefit to 1 x `m3.xlarge` usage, because each `m3.xlarge` instance is equivalent to 8 normalized units/hour. The remaining `m3.xlarge` usage is charged at the On-Demand rate. ### Scenario 3: Regional Reserved Instances in linked accounts Reserved Instances are first applied to usage within the purchasing account, followed by qualifying usage in any other account in the organization. For more information, see [Reserved Instances and consolidated billing](concepts-reserved-instances-application.md#concepts-reserved-instances-billing). For regional Reserved Instances that offer instance size flexibility, the benefit is applied from the smallest to the largest instance size within the instance family. You're running the following On-Demand Instances in account A (the purchasing account): + 2 x `m4.xlarge` Linux, default tenancy instances in Availability Zone us-east-1a + 1 x `m4.2xlarge` Linux, default tenancy instances in Availability Zone us-east-1b + 2 x `c4.xlarge` Linux, default tenancy instances in Availability Zone us-east-1a + 1 x `c4.2xlarge` Linux, default tenancy instances in Availability Zone us-east-1b Another customer is running the following On-Demand Instances in account B—a linked account: + 2 x `m4.xlarge` Linux, default tenancy instances in Availability Zone us-east-1a You purchase the following regional Reserved Instances in account A: + 4 x `m4.xlarge` Linux, default tenancy Reserved Instances in Region us-east-1 + 2 x `c4.xlarge` Linux, default tenancy Reserved Instances in Region us-east-1 The regional Reserved Instance benefits are applied in the following way: + The discount of the four `m4.xlarge` Reserved Instances is used by the two `m4.xlarge` instances and the single `m4.2xlarge` instance in account A (purchasing account). All three instances match the attributes (instance family, Region, platform, tenancy). The discount is applied to instances in the purchasing account (account A) first, even though account B (linked account) has two `m4.xlarge` that also match the Reserved Instances. There is no capacity reservation because the Reserved Instances are regional Reserved Instances. + The discount of the two `c4.xlarge` Reserved Instances applies to the two `c4.xlarge` instances, because they are a smaller instance size than the `c4.2xlarge` instance. There is no capacity reservation because the Reserved Instances are regional Reserved Instances. ### Scenario 4: Zonal Reserved Instances in a linked account In general, Reserved Instances that are owned by an account are applied first to usage in that account. However, if there are qualifying, unused Reserved Instances for a specific Availability Zone (zonal Reserved Instances) in other accounts in the organization, they are applied to the account before regional Reserved Instances owned by the account. This is done to ensure maximum Reserved Instance utilization and a lower bill. For billing purposes, all the accounts in the organization are treated as one account. The following example might help explain this. You're running the following On-Demand Instance in account A (the purchasing account): + 1 x `m4.xlarge` Linux, default tenancy instance in Availability Zone us-east-1a A customer is running the following On-Demand Instance in linked account B: + 1 x `m4.xlarge` Linux, default tenancy instance in Availability Zone us-east-1b You purchase the following regional Reserved Instances in account A: + 1 x `m4.xlarge` Linux, default tenancy Reserved Instance in Region us-east-1 A customer also purchases the following zonal Reserved Instances in linked account C: + 1 x `m4.xlarge` Linux, default tenancy Reserved Instances in Availability Zone us-east-1a The Reserved Instance benefits are applied in the following way: + The discount of the `m4.xlarge` zonal Reserved Instance owned by account C is applied to the `m4.xlarge` usage in account A. + The discount of the `m4.xlarge` regional Reserved Instance owned by account A is applied to the `m4.xlarge` usage in account B. + If the regional Reserved Instance owned by account A was first applied to the usage in account A, the zonal Reserved Instance owned by account C remains unused and usage in account B is charged at On-Demand rates. For more information, see [Understanding your reservations](https://docs.aws.amazon.com/cur/latest/userguide/understanding-ri.html) in the AWS Cost and Usage Report. **Note** Zonal Reserved Instances reserve capacity only for the owning account and cannot be shared with other AWS accounts. If you need to share capacity with other AWS accounts, use [Reserve compute capacity with EC2 On-Demand Capacity Reservations](ec2-capacity-reservations.md). # Use your Reserved Instances Reserved Instances are automatically applied to running On-Demand Instances provided that the specifications match. If you have no running On-Demand Instances that match the specifications of your Reserved Instance, the Reserved Instance is unused until you launch an instance with the required specifications. If you're launching an On-Demand Instance to take advantage of the billing benefit of a Reserved Instance, ensure that you specify the following information when you configure your On-Demand Instance: **Platform** You must specify an Amazon Machine Image (AMI) that matches the platform (product description) of your Reserved Instance. For example, if you specified `Linux/UNIX` for your Reserved Instance, you can launch an instance from an Amazon Linux AMI or an Ubuntu AMI. **Instance type** If you purchased a zonal Reserved Instance, you must specify the same instance type as your Reserved Instance; for example, `t3.large`. For more information, see [How zonal Reserved Instances are applied](apply_ri.md#apply-zonal-ri). If you purchased a regional Reserved Instance, you must specify an instance type from the same instance family as the instance type of your Reserved Instance. For example, if you specified `t3.xlarge` for your Reserved Instance, you must launch your instance from the T3 family, but you can specify any size, for example, `t3.medium`. For more information, see [How regional Reserved Instances are applied](apply_ri.md#apply-regional-ri). **Availability Zone** If you purchased a zonal Reserved Instance for a specific Availability Zone, you must launch the instance into the same Availability Zone. If you purchased a regional Reserved Instance, you can launch the instance into any Availability Zone in the Region that you specified for the Reserved Instance. **Tenancy** The tenancy (`dedicated` or `shared`) of the instance must match the tenancy of your Reserved Instance. For more information, see [Amazon EC2 Dedicated Instances](dedicated-instance.md). For examples of how Reserved Instances are applied to your running On-Demand Instances, see [How Reserved Instance discounts are applied](apply_ri.md). For more information, see [Why aren't my Amazon EC2 Reserved Instances applying to my AWS billing in the way that I expected?](https://repost.aws/knowledge-center/reserved-instance-applying-why) You can use various methods to launch the On-Demand Instances that use your Reserved Instance discount. For information about the different launch methods, see [Launch an Amazon EC2 instance](LaunchingAndUsingInstances.md). You can also use Amazon EC2 Auto Scaling to launch an instance. For more information, see the [Amazon EC2 Auto Scaling User Guide](https://docs.aws.amazon.com/autoscaling/ec2/userguide/). # How billing works with Reserved Instances All Reserved Instances provide you with a discount compared to On-Demand pricing. With Reserved Instances, you pay for the entire term regardless of actual use. You can choose to pay for your Reserved Instance upfront, partially upfront, or monthly, depending on the [payment option](ec2-reserved-instances.md#ri-payment-options) specified for the Reserved Instance. When Reserved Instances expire, you are charged On-Demand rates for EC2 instance usage. You can queue a Reserved Instance for purchase up to three years in advance. This can help you ensure that you have uninterrupted coverage. For more information, see [Queue your purchase](ri-market-concepts-buying.md#ri-queued-purchase). The AWS Free Tier is available for new AWS accounts. If you are using the AWS Free Tier to run Amazon EC2 instances, and you purchase a Reserved Instance, you are charged the standard pricing. For information, see [AWS Free Tier](https://aws.amazon.com/free/). **Topics** + [ ## Usage billing ](#hourly-billing) + [ ## Viewing your bill ](#ri-market-buyer-billing) + [ ## Reserved Instances and consolidated billing ](#concepts-reserved-instances-billing) + [ ## Reserved Instance discount pricing tiers ](#reserved-instances-discounts) ## Usage billing Reserved Instances are billed for every clock-hour during the term that you select, regardless of whether an instance is running. Each clock-hour starts on the hour (zero minutes and zero seconds past the hour) of a standard 24-hour clock. For example, 1:00:00 to 1:59:59 is one clock-hour. For more information about instance states, see [Amazon EC2 instance state changes](ec2-instance-lifecycle.md). A Reserved Instance billing benefit can be applied to a running instance on a per-second basis. Per-second billing is available for instances using an open-source Linux distribution, such as Amazon Linux and Ubuntu. Per-hour billing is used for commercial Linux distributions, such as Red Hat Enterprise Linux and SUSE Linux Enterprise Server. A Reserved Instance billing benefit can apply to a maximum of 3600 seconds (one hour) of instance usage per clock-hour. You can run multiple instances concurrently, but can only receive the benefit of the Reserved Instance discount for a total of 3600 seconds per clock-hour; instance usage that exceeds 3600 seconds in a clock-hour is billed at the On-Demand rate. For example, if you purchase one `m4.xlarge` Reserved Instance and run four `m4.xlarge` instances concurrently for one hour, one instance is charged at one hour of Reserved Instance usage and the other three instances are charged at three hours of On-Demand usage. However, if you purchase one `m4.xlarge` Reserved Instance and run four `m4.xlarge` instances for 15 minutes (900 seconds) each within the same hour, the total running time for the instances is one hour, which results in one hour of Reserved Instance usage and 0 hours of On-Demand usage. ![\[Four m4.xlarge instances running for 15 minutes each within the same hour.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-per-second-billing.png) If multiple eligible instances are running concurrently, the Reserved Instance billing benefit is applied to all the instances at the same time up to a maximum of 3600 seconds in a clock-hour; thereafter, On-Demand rates apply. ![\[Multiple instances running concurrently with Reserved Instance billing.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-per-second-billing-concurrent.png) **Cost Explorer** on the [Billing and Cost Management](https://console.aws.amazon.com/billing) console enables you to analyze the savings against running On-Demand Instances. The [Reserved Instances FAQ](https://aws.amazon.com/ec2/faqs/#reserved-instances) includes an example of a list value calculation. If you close your AWS account, On-Demand billing for your resources stops. However, if you have any Reserved Instances in your account, you continue to receive a bill for these until they expire. ## Viewing your bill You can find out about the charges and fees to your account by viewing the [AWS Billing and Cost Management](https://console.aws.amazon.com/billing) 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 Reserved Instances. You can view the charges online, or you can download a CSV file. You can also track your Reserved Instance utilization using the AWS Cost and Usage Report. For more information, see [Understanding your reservations](https://docs.aws.amazon.com/cur/latest/userguide/understanding-ri.html). ## Reserved Instances and consolidated billing The pricing benefits of Reserved Instances are shared when the purchasing account is part of a set of accounts billed under one consolidated billing payer account. The instance usage across all member accounts is aggregated in the payer account every month. This is typically useful for companies in which there are different functional teams or groups; then, the normal Reserved Instance logic is applied to calculate the bill. For more information, see [Consolidated billing for AWS Organizations](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html). If you close the account that purchased the Reserved Instance, the payer account is charged for the Reserved Instance until the Reserved Instance expires. After the closed account is permanently deleted in 90 days, the member accounts no longer benefit from the Reserved Instance billing discount. **Note** Zonal Reserved Instances reserve capacity only for the owning account and cannot be shared with other AWS accounts. If you need to share capacity with other AWS accounts, use [Reserve compute capacity with EC2 On-Demand Capacity Reservations](ec2-capacity-reservations.md). ## Reserved Instance discount pricing tiers If your account qualifies for a discount pricing tier, it automatically receives discounts on upfront and instance usage fees for Reserved Instance purchases that you make within that tier level from that point on. To qualify for a discount, the list value of your Reserved Instances in the Region must be \$1500,000 USD or more. The following rules apply: + Pricing tiers and related discounts apply only to purchases of Amazon EC2 Standard Reserved Instances. + Pricing tiers do not apply to Reserved Instances for Windows with SQL Server Standard, SQL Server Web, and SQL Server Enterprise. + Pricing tiers do not apply to Reserved Instances for Linux with SQL Server of any kind. + Pricing tier discounts only apply to purchases made from AWS. They do not apply to purchases of third-party Reserved Instances. + Discount pricing tiers are currently not applicable to Convertible Reserved Instance purchases. **Topics** + [ ### Calculate Reserved Instance pricing discounts ](#pricing-discounts) + [ ### Buy with a discount tier ](#buying-discount-tier) + [ ### Crossing pricing tiers ](#crossing-pricing-tiers) + [ ### Consolidated billing for pricing tiers ](#consolidating-billing) ### Calculate Reserved Instance pricing discounts You can determine the pricing tier for your account by calculating the list value for all of your Reserved Instances in a Region. Multiply the hourly recurring price for each reservation by the total number of hours for the term and add the undiscounted upfront price (also known as the fixed price) at the time of purchase. Because the list value is based on undiscounted (public) pricing, it is not affected if you qualify for a volume discount or if the price drops after you buy your Reserved Instances. ``` List value = fixed price + (undiscounted recurring hourly price * hours in term) ``` For example, for a 1-year Partial Upfront `t2.small` Reserved Instance, assume the upfront price is \$160.00 and the hourly rate is \$10.007. This provides a list value of \$1121.32. ``` 121.32 = 60.00 + (0.007 * 8760) ``` **To view the fixed price values for Reserved Instances 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 **Reserved Instances**. 1. To display the **Upfront price** column, choose settings ( ![\[Settings icon.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/settings-icon.png) ) in the top-right corner, turn on **Upfront price**, and choose **Confirm**. **To view the fixed price values for Reserved Instances using the command line** + [describe-reserved-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances.html) (AWS CLI) + [Get-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstance.html) (AWS Tools for Windows PowerShell) ### Buy with a discount tier When you buy Reserved Instances, Amazon EC2 automatically applies any discounts to the part of your purchase that falls within a discount pricing tier. You don't need to do anything differently, and you can buy Reserved Instances using any of the Amazon EC2 tools. For more information, see [Buy Reserved Instances for Amazon EC2](ri-market-concepts-buying.md). After the list value of your active Reserved Instances in a Region crosses into a discount pricing tier, any future purchase of Reserved Instances in that Region are charged at a discounted rate. If a single purchase of Reserved Instances in a Region takes you over the threshold of a discount tier, then the portion of the purchase that is above the price threshold is charged at the discounted rate. For more information about the temporary Reserved Instance IDs that are created during the purchase process, see [Crossing pricing tiers](#crossing-pricing-tiers). If your list value falls below the price point for that discount pricing tier—for example, if some of your Reserved Instances expire—future purchases of Reserved Instances in the Region are not discounted. However, you continue to get the discount applied against any Reserved Instances that were originally purchased within the discount pricing tier. When you buy Reserved Instances, one of four possible scenarios occurs: + **No discount**—Your purchase within a Region is still below the discount threshold. + **Partial discount**—Your purchase within a Region crosses the threshold of the first discount tier. No discount is applied to one or more reservations and the discounted rate is applied to the remaining reservations. + **Full discount**—Your entire purchase within a Region falls within one discount tier and is discounted appropriately. + **Two discount rates**—Your purchase within a Region crosses from a lower discount tier to a higher discount tier. You are charged two different rates: one or more reservations at the lower discounted rate, and the remaining reservations at the higher discounted rate. ### Crossing pricing tiers If your purchase crosses into a discounted pricing tier, you see multiple entries for that purchase: one for that part of the purchase charged at the regular price, and another for that part of the purchase charged at the applicable discounted rate. The Reserved Instance service generates several Reserved Instance IDs because your purchase crossed from an undiscounted tier, or from one discounted tier to another. There is an ID for each set of reservations in a tier. Consequently, the ID returned by your purchase CLI command or API action is different from the actual ID of the new Reserved Instances. ### Consolidated billing for pricing tiers A consolidated billing account aggregates the list value of member accounts within a Region. When the list value of all active Reserved Instances for the consolidated billing account reaches a discount pricing tier, any Reserved Instances purchased after this point by any member of the consolidated billing account are charged at the discounted rate (as long as the list value for that consolidated account stays above the discount pricing tier threshold). For more information, see [Reserved Instances and consolidated billing](#concepts-reserved-instances-billing). # Buy Reserved Instances for Amazon EC2 Buy Reserved Instances To buy a Reserved Instance for Amazon EC2, you can use the Amazon EC2 console, a command line tool, or an SDK to search for Reserved Instance offerings from AWS and third-party sellers, adjusting your search parameters until you find the exact match that you're looking for. When you search for Reserved Instances to buy, you receive a quote on the cost of the returned offerings. When you proceed with the purchase, AWS automatically places a limit price on the purchase price. The total cost of your Reserved Instances won't exceed the amount that you were quoted. If the price rises or changes for any reason, the purchase is not completed. When you are purchasing a third-party seller’s Reserved Instance from the Amazon EC2 Reserved Instance Marketplace, if there are offerings similar to your choice but at a lower upfront price, AWS sells you the offerings at the lower upfront price. Before you confirm your purchase, review the details of the Reserved Instance that you plan to buy, and make sure that all the parameters are accurate. After you purchase a Reserved Instance (either from a third-party seller in the Reserved Instance Marketplace or from AWS), you cannot cancel your purchase. You can queue a purchase for a future date, and cancel the queued purchase before its scheduled time. To purchase and modify Reserved Instances, ensure that your user has the appropriate permissions, such as the ability to describe Availability Zones. For information, see [Example: Work with Reserved Instances](ExamplePolicies_EC2.md#iam-example-reservedinstances) (API) or [Example: Work with Reserved Instances](iam-policies-ec2-console.md#ex-reservedinstances) (console). **Topics** + [ ## Choosing a platform ](#ri-choosing-platform) + [ ## Queue your purchase ](#ri-queued-purchase) + [ ## Buy Standard Reserved Instances ](#ri-buying-standard) + [ ## Buy Convertible Reserved Instances ](#ri-buying-convertible) + [ ## Buy from the Reserved Instance Marketplace ](#ri-market-buying-guide) + [ ## Cancel a queued purchase ](#cancel-queued-purchase) + [ ## Renew a Reserved Instance ](#renew-ri) ## Choosing a platform Amazon EC2 supports the following platforms for Reserved Instances: + Linux/UNIX + Linux with SQL Server Standard + Linux with SQL Server Web + Linux with SQL Server Enterprise + SUSE Linux + Red Hat Enterprise Linux + Red Hat Enterprise Linux with HA + Windows + Windows with SQL Server Standard + Windows with SQL Server Web + Windows with SQL Server Enterprise **Considerations** + If you bring your existing subscription (BYOS) for **Red Hat Enterprise Linux**, **SUSE Linux**, or **Ubuntu Pro**, you must choose an offering for the **Linux/Unix** platform. + Reserved Instances are not supported on instances running **macOS** or Ubuntu Pro (EC2 subscription-included, i.e., not BYOS). For saving with On-Demand instance pricing, we recommend that you use macOS and Ubuntu Pro (EC2 subscription-included) instances with Savings Plans. For more information, see [Savings Plans User Guide](https://docs.aws.amazon.com/savingsplans/latest/userguide/what-is-savings-plans.html). To ensure that an instance runs in a specific Reserved Instance, the platform of the Reserved Instance 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-id 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 ``` ------ ## Queue your purchase By default, when you purchase a Reserved Instance, the purchase is made immediately. Alternatively, you can queue your purchases for a future date and time. For example, you can queue a purchase for around the time that an existing Reserved Instance expires. This can help you ensure that you have uninterrupted coverage. You can queue purchases for regional Reserved Instances, but not zonal Reserved Instances or Reserved Instances from other sellers. You can queue a purchase up to three years in advance. On the scheduled date and time, the purchase is made using the default payment method. After the payment is successful, the billing benefit is applied. You can set a date for your queued purchases in the Amazon EC2 console, and the purchase is queued until 00:00 UTC on this date. To specify a different time for the queued purchase, use an AWS SDK or command line tool. You can view your queued purchases in the Amazon EC2 console. The status of a queued purchase is **queued**. You can cancel a queued purchase any time before its scheduled time. For details, see [Cancel a queued purchase](#cancel-queued-purchase). ## Buy Standard Reserved Instances You can buy Standard Reserved Instances in a specific Availability Zone and get a capacity reservation. Alternatively, you can forego the capacity reservation and purchase a regional Standard Reserved Instance. After the purchase is complete, if you already have a running instance that matches the specifications of the Reserved Instance, the billing benefit is immediately applied. You do not need to restart your instances. If you do not have a suitable running instance, launch an instance and ensure that you match the exact criteria that you specified for your Reserved Instance. For more information, see [Use your Reserved Instances](using-reserved-instances.md). For examples of how Reserved Instances are applied to your running instances, see [How Reserved Instance discounts are applied](apply_ri.md). ------ #### [ Console ] **To buy Standard Reserved Instances** 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 **Reserved Instances**, and then choose **Purchase Reserved Instances**. 1. For **Offering class**, choose **Standard** to display Standard Reserved Instances. 1. To purchase a capacity reservation, toggle on **Only show offerings that reserve capacity** in the top-right corner of the purchase screen. When you toggle on this setting, the **Availability Zone** field appears. To purchase a regional Reserved Instance, toggle off this setting. When you toggle off this setting, the **Availability Zone** field disappears. 1. Select other configurations as needed, and then choose **Search**. 1. For each Reserved Instance that you want to purchase, enter the desired quantity, and choose **Add to cart**. To purchase a Standard Reserved Instance from the Reserved Instance Marketplace, look for **3rd party** in the **Seller** column in the search results. The **Term** column displays non-standard terms. For more information, see [Buy from the Reserved Instance Marketplace](#ri-market-buying-guide). 1. To see a summary of the Reserved Instances that you selected, choose **View cart**. 1. If **Order on** is **Now**, the purchase is completed immediately after you choose **Order all**. To queue a purchase, choose **Now** and select a date. You can select a different date for each eligible offering in the cart. The purchase is queued until 00:00 UTC on the selected date. 1. To complete the order, choose **Order all**. If, at the time of placing the order, there are offerings similar to your choice but with a lower price, AWS sells you the offerings at the lower price. 1. Choose **Close**. The status of your order is listed in the **State** column. When your order is complete, the **State** value changes from `Payment-pending` to `Active`. When the Reserved Instance is `Active`, it is ready to use. If the status goes to `Retired`, AWS might not have received your payment. ------ #### [ AWS CLI ] **To buy a Standard Reserved Instance** 1. Find available Reserved Instances using the [describe-reserved-instances-offerings](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances-offerings.html) command. Specify `standard` for the `--offering-class` option to return only Standard Reserved Instances. You can apply additional criteria to narrow your results. For example, use the following command to purchase a regional `t2.large` Reserved Instance with a default tenancy for `Linux/UNIX` for a 1-year term only. ``` aws ec2 describe-reserved-instances-offerings \ --instance-type t2.large \ --offering-class standard \ --product-description "Linux/UNIX" \ --instance-tenancy default \ --filters Name=duration,Values=31536000 \ Name=scope,Values=Region ``` To find Reserved Instances on the Reserved Instance Marketplace only, use the `marketplace` filter and do not specify a duration in the request, as the term might be shorter than a 1– or 3-year term. ``` aws ec2 describe-reserved-instances-offerings \ --instance-type t2.large \ --offering-class standard \ --product-description "Linux/UNIX" \ --instance-tenancy default \ --filters Name=marketplace,Values=true ``` When you find a Reserved Instance that meets your needs, take note of the offering ID. For example: ``` "ReservedInstancesOfferingId": "bec624df-a8cc-4aad-a72f-4f8abc34caf2" ``` 1. Use the [purchase-reserved-instances-offering](https://docs.aws.amazon.com/cli/latest/reference/ec2/purchase-reserved-instances-offering.html) command to buy your Reserved Instance. You must specify the Reserved Instance offering ID you obtained the previous step and you must specify the number of instances for the reservation. ``` aws ec2 purchase-reserved-instances-offering \ --reserved-instances-offering-id bec624df-a8cc-4aad-a72f-4f8abc34caf2 \ --instance-count 1 ``` By default, the purchase is completed immediately. Alternatively, to queue the purchase, add the following option to the previous call. ``` --purchase-time "2020-12-01T00:00:00Z" ``` 1. Use the [describe-reserved-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances.html) command to get the status of your Reserved Instance. ``` aws ec2 describe-reserved-instances \ --reserved-instances-ids b847fa93-e282-4f55-b59a-1342fec06327 \ --query ReservedInstances[].State ``` ------ #### [ PowerShell ] **To buy a Standard Reserved Instance** 1. Find available Reserved Instances using the [Get-EC2ReservedInstancesOffering](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstancesOffering.html) cmdlet. Specify `standard` for the `-OfferingClass` parameter to return only Standard Reserved Instances. You can apply additional criteria to narrow your results. For example, use the following command to purchase a regional `t2.large` Reserved Instance with a default tenancy for `Linux/UNIX` for a 1-year term only. ``` Get-EC2ReservedInstancesOffering ` -InstanceType "t2.large" ` -OfferingClass "standard" ` -ProductDescription "Linux/UNIX" ` -InstanceTenancy "default" ` -Filters @{Name="duration"; Values="31536000"} ` @{Name="scope"; Values="Region" ``` To find Reserved Instances on the Reserved Instance Marketplace only, use the `marketplace` filter and do not specify a duration in the request, as the term might be shorter than a 1– or 3-year term. ``` Get-EC2ReservedInstancesOffering ` -InstanceType t2.large ` -OfferingClass "standard" ` -ProductDescription "Linux/UNIX" ` -InstanceTenancy default ` -Filters @{Name="marketplace"; Values="true"} ``` When you find a Reserved Instance that meets your needs, take note of the offering ID. For example: ``` bec624df-a8cc-4aad-a72f-4f8abc34caf2 ``` 1. Use the [New-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2ReservedInstance.html) cmdlet to buy your Reserved Instance. You must specify the Reserved Instance offering ID you obtained the previous step and you must specify the number of instances for the reservation. ``` New-EC2ReservedInstance ` -ReservedInstancesOfferingId "bec624df-a8cc-4aad-a72f-4f8abc34caf2" ` -InstanceCount 1 ``` By default, the purchase is completed immediately. Alternatively, to queue the purchase, add the following parameter to the previous call. ``` -PurchaseTime "2020-12-01T00:00:00Z" ``` 1. Use the [Get-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstance.html) cmdlet to get the status of your Reserved Instance. ``` Get-EC2ReservedInstance ` -ReservedInstancesId b847fa93-e282-4f55-b59a-1342fec06327 | ` Select State ``` ------ ## Buy Convertible Reserved Instances You can buy Convertible Reserved Instances in a specific Availability Zone and get a capacity reservation. Alternatively, you can forego the capacity reservation and purchase a regional Convertible Reserved Instance. If you already have a running instance that matches the specifications of the Reserved Instance, the billing benefit is immediately applied. You do not have to restart your instances. If you do not have a suitable running instance, launch an instance and ensure that you match the same criteria that you specified for your Reserved Instance. For more information, see [Use your Reserved Instances](using-reserved-instances.md). For examples of how Reserved Instances are applied to your running instances, see [How Reserved Instance discounts are applied](apply_ri.md). ------ #### [ Console ] **To buy Convertible Reserved Instances** 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 **Reserved Instances**, and then choose **Purchase Reserved Instances**. 1. For **Offering class**, choose **Convertible** to display Convertible Reserved Instances. 1. To purchase a capacity reservation, toggle on **Only show offerings that reserve capacity** in the top-right corner of the purchase screen. When you toggle on this setting, the **Availability Zone** field appears. To purchase a regional Reserved Instance, toggle off this setting. When you toggle off this setting, the **Availability Zone** field disappears. 1. Select other configurations as needed and choose **Search**. 1. For each Convertible Reserved Instance that you want to purchase, enter the quantity, and choose **Add to cart**. 1. To see a summary of your selection, choose **View cart**. 1. If **Order on** is **Now**, the purchase is completed immediately after you choose **Order all**. To queue a purchase, choose **Now** and select a date. You can select a different date for each eligible offering in the cart. The purchase is queued until 00:00 UTC on the selected date. 1. To complete the order, choose **Order all**. If, at the time of placing the order, there are offerings similar to your choice but with a lower price, AWS sells you the offerings at the lower price. 1. Choose **Close**. The status of your order is listed in the **State** column. When your order is complete, the **State** value changes from `Payment-pending` to `Active`. When the Reserved Instance is `Active`, it is ready to use. If the status goes to `Retired`, AWS might not have received your payment. ------ #### [ AWS CLI ] **To buy a Convertible Reserved Instance** 1. Find available Reserved Instances using the [describe-reserved-instances-offerings](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances-offerings.html) command. Specify `convertible` for the `--offering-class` option to return only Convertible Reserved Instances. You can apply additional criteria to narrow your results. For example, use the following command to purchase a regional `t2.large` Reserved Instance with a default tenancy for `Linux/UNIX`. ``` aws ec2 describe-reserved-instances-offerings \ --instance-type t2.large \ --offering-class convertible \ --product-description "Linux/UNIX" \ --instance-tenancy default \ --filters Name=scope,Values=Region ``` When you find a Reserved Instance that meets your needs, take note of the offering ID. For example: ``` "ReservedInstancesOfferingId": "bec624df-a8cc-4aad-a72f-4f8abc34caf2" ``` 1. Use the [purchase-reserved-instances-offering](https://docs.aws.amazon.com/cli/latest/reference/ec2/purchase-reserved-instances-offering.html) command to buy your Reserved Instance. You must specify the Reserved Instance offering ID you obtained the previous step and you must specify the number of instances for the reservation. ``` aws ec2 purchase-reserved-instances-offering \ --reserved-instances-offering-id bec624df-a8cc-4aad-a72f-4f8abc34caf2 \ --instance-count 1 ``` By default, the purchase is completed immediately. Alternatively, to queue the purchase, add the following option to the previous call. ``` --purchase-time "2020-12-01T00:00:00Z" ``` 1. Use the [describe-reserved-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances.html) command to get the status of your Reserved Instance. ``` aws ec2 describe-reserved-instances \ --reserved-instances-ids b847fa93-e282-4f55-b59a-1342fec06327 \ --query ReservedInstances[].State ``` ------ #### [ PowerShell ] **To buy a Convertible Reserved Instance** 1. Find available Reserved Instances using the [Get-EC2ReservedInstancesOffering](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstancesOffering.html) cmdlet. Specify `convertible` for the `-OfferingClass` parameter to return only Convertible Reserved Instances. You can apply additional criteria to narrow your results. For example, use the following command to purchase a regional `t2.large` Reserved Instance with a default tenancy for `Linux/UNIX`. ``` Get-EC2ReservedInstancesOffering ` -InstanceType "t2.large" ` -OfferingClass "convertible" ` -ProductDescription "Linux/UNIX" ` -InstanceTenancy "default" ` -Filters @{Name="scope"; Values="Region" ``` When you find a Reserved Instance that meets your needs, take note of the offering ID. For example: ``` bec624df-a8cc-4aad-a72f-4f8abc34caf2 ``` 1. Use the [New-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2ReservedInstance.html) cmdlet to buy your Reserved Instance. You must specify the Reserved Instance offering ID that you obtained the previous step and you must specify the number of instances for the reservation. ``` New-EC2ReservedInstance ` -ReservedInstancesOfferingId "bec624df-a8cc-4aad-a72f-4f8abc34caf2" ` -InstanceCount 1 ``` By default, the purchase is completed immediately. Alternatively, to queue the purchase, add the following parameter to the previous call. ``` -PurchaseTime "2020-12-01T00:00:00Z" ``` 1. Use the [Get-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstance.html) cmdlet to get the status of your Reserved Instance. ``` Get-EC2ReservedInstance ` -ReservedInstancesId b847fa93-e282-4f55-b59a-1342fec06327 | ` Select State ``` ------ ## Buy from the Reserved Instance Marketplace You can purchase Reserved Instances from third-party sellers who own Reserved Instances that they no longer need from the Reserved Instance Marketplace. You can do this using the Amazon EC2 console or a command line tool. The process is similar to purchasing Reserved Instances from AWS. For more information, see [Buy Standard Reserved Instances](#ri-buying-standard). There are a few differences between Reserved Instances purchased in the Reserved Instance Marketplace and Reserved Instances purchased directly from AWS: + **Term** – Reserved Instances that you purchase from third-party sellers have less than a full standard term remaining. Full standard terms from AWS run for one year or three years. + **Upfront price** – Third-party Reserved Instances can be sold at different upfront prices. The usage or recurring fees remain the same as the fees set when the Reserved Instances were originally purchased from AWS. + **Types of Reserved Instances** – Only Amazon EC2 Standard Reserved Instances can be purchased from the Reserved Instance Marketplace. Convertible Reserved Instances, Amazon RDS, and Amazon ElastiCache Reserved Instances are not available for purchase on the Reserved Instance Marketplace. Basic information about you is shared with the seller, for example, your ZIP code and country information. This information enables sellers to calculate any necessary transaction taxes that they have to remit to the government (such as sales tax or value-added tax) and is provided as a disbursement report. In rare circumstances, AWS might have to provide the seller with your email address, so that they can contact you regarding questions related to the sale (for example, tax questions). For similar reasons, AWS shares the legal entity name of the seller on the buyer's purchase invoice. If you need additional information about the seller for tax or related reasons, contact [Support](https://aws.amazon.com/contact-us/). ## Cancel a queued purchase You can queue a purchase up to three years in advance. You can cancel a queued purchase any time before its scheduled time. ------ #### [ Console ] **To cancel a queued purchase** 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 **Reserved Instances**. 1. Select one or more Reserved Instances. 1. Choose **Actions**, **Delete queued Reserved Instances**. 1. When prompted for confirmation, choose **Delete**, and then **Close**. ------ #### [ AWS CLI ] **To cancel a queued purchase** Use the [delete-queued-reserved-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/delete-queued-reserved-instances.html) command. ``` aws ec2 delete-queued-reserved-instances \ --reserved-instances-ids b847fa93-e282-4f55-b59a-1342fec06327 ``` ------ #### [ PowerShell ] **To cancel a queued purchase** Use the [Remove-EC2QueuedReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Remove-EC2QueuedReservedInstance.html) cmdlet. ``` Remove-EC2QueuedReservedInstance ` -ReservedInstancesId b847fa93-e282-4f55-b59a-1342fec06327 ``` ------ ## Renew a Reserved Instance You can renew a Reserved Instance before it is scheduled to expire. Renewing a Reserved Instance queues the purchase of a Reserved Instance with the same configuration until the current Reserved Instance expires. You must renew a Reserved Instance using the Amazon EC2 console. **To renew a Reserved Instance using a queued purchase** 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 **Reserved Instances**. 1. Select the Reserved Instance to renew. 1. Choose **Actions**, **Renew Reserved Instances**. 1. To complete the order, choose **Order all**, and then **Close**. # Sell Reserved Instances for Amazon EC2 in the Reserved Instance Marketplace Sell Reserved Instances The Amazon EC2 Reserved Instance Marketplace is a platform that facilitates the sale of unused Standard Reserved Instances from AWS customers and third-party sellers. These Reserved Instances can vary in term lengths and pricing options. You might want to sell your Reserved Instances when you no longer need them, such as when you move your instances to a new AWS Region, change to a different instance type, finish projects before the Reserved Instance term expires, your business needs change, or you have excess capacity. As soon as you list your Reserved Instances in the Reserved Instance Marketplace, they are available for potential buyers to find. All Reserved Instances are grouped according to the duration of the term remaining and the hourly price. To fulfill a buyer's request to purchase a third-party seller’s Reserved Instance via the Reserved Instance Marketplace, AWS first sells the Reserved Instance with the lowest upfront price in the specified grouping. Then, AWS sells the Reserved Instance with the next lowest price, until the buyer's entire order is fulfilled. AWS then processes the transactions and transfers ownership of the Reserved Instances to the buyer. You own your Reserved Instance until it's sold. After the sale, you've given up the capacity reservation and the discounted recurring fees. If you continue to use your instance, AWS charges you the On-Demand price starting from the time that your Reserved Instance was sold. If you want to sell your unused Reserved Instances on the Reserved Instance Marketplace, you must meet certain eligibility criteria. For information about buying Reserved Instances on the Reserved Instance Marketplace, see [Buy from the Reserved Instance Marketplace](ri-market-concepts-buying.md#ri-market-buying-guide). **Topics** + [ ## Restrictions and limitations ](#ri-seller-limits) + [ ## Register as a seller ](#ri-market-seller-profile) + [ ## Bank account for disbursement ](#ri-market-concepts-bank) + [ ## Tax information ](#ri-market-concepts-taxinfo) + [ ## Price your Reserved Instances ](#ri-market-concepts-pricing) + [ ## List your Reserved Instances ](#ri-market-selling-listing) + [ ## Reserved Instance listing states ](#ri-listing-states) + [ ## Lifecycle of a listing ](#ri-market-concepts-sold-partial) + [ ## After your Reserved Instance is sold ](#ri-market-concepts-sold) + [ ## Getting paid ](#ri-market-sold-gettingpaid) + [ ## Information shared with the buyer ](#ri-market-seller-disclosure) ## Restrictions and limitations Before you can sell your unused reservations, you must register as a seller in the Reserved Instance Marketplace. For information, see [Register as a seller](#ri-market-seller-profile). The following limitations and restrictions apply when selling Reserved Instances: + Only Amazon EC2 Standard regional and zonal Reserved Instances can be sold in the Reserved Instance Marketplace. + Amazon EC2 Convertible Reserved Instances can't be sold in the Reserved Instance Marketplace. + Reserved Instances for other AWS services, such as Amazon RDS and Amazon ElastiCache, cannot be sold in the Reserved Instance Marketplace. + There must be at least one month remaining in the term of the Standard Reserved Instance. + You can't sell a Standard Reserved Instance in a Region that is [disabled by default](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html). + The minimum price allowed in the Reserved Instance Marketplace is \$10.00. + You can sell No Upfront, Partial Upfront, or All Upfront Reserved Instances in the Reserved Instance Marketplace as long as they have been active in your account for at least 30 days. Additionally, if there is an upfront payment on a Reserved Instance, it can only be sold after AWS has received the upfront payment. + You can't sell a Reserved Instance in the Reserved Instance Marketplace if you purchased it using a volume discount. + You cannot modify your listing in the Reserved Instance Marketplace directly. However, you can change your listing by first canceling it and then creating another listing with new parameters. For information, see [Price your Reserved Instances](#ri-market-concepts-pricing). You can also modify your Reserved Instances before listing them. For information, see [Modify Reserved Instances](ri-modifying.md). + AWS charges a service fee of 12 percent of the total upfront price of each Standard Reserved Instance you sell in the Reserved Instance Marketplace. The upfront price is the price the seller is charging for the Standard Reserved Instance. + When you register as a seller, the bank you specify must have a US address. For more information, see [Additional seller requirements for paid products](https://docs.aws.amazon.com/marketplace/latest/userguide/user-guide-for-sellers.html#additional-seller-requirements-for-paid-products) in the *AWS Marketplace Seller Guide*. + Amazon Web Services India Private Limited (AWS India) customers can't register as a seller on EC2 Reserved Instance Marketplace and can't list or sell Reserved Instances in the EC2 Reserved Instance Marketplace, even if they have a US bank account. For more information, see [What are the differences between AWS accounts and AWS India accounts?](https://repost.aws/knowledge-center/aws-india-differences) + If you change your seller of record to Amazon Web Services India Private Limited (AWS India), you'll be deregistered as a seller from the EC2 Reserved Instance Marketplace and all of your existing active listings on the EC2 Reserved Instance Marketplace will be removed. To restore your seller status, you must change your account location to a country other than India and complete the seller registration process again. ## Register as a seller **Note** Only the AWS account root user can register an account as a seller. To sell in the Reserved Instance Marketplace, you must first register as a seller. During registration, you provide the following information: + **Bank information**—AWS must have your bank information in order to disburse funds collected when you sell your reservations. The bank you specify must have a US address. For more information, see [Bank account for disbursement](#ri-market-concepts-bank). + **Tax information**—All sellers are required to complete a tax information interview to determine any necessary tax reporting obligations. For more information, see [Tax information](#ri-market-concepts-taxinfo). After AWS receives your completed seller registration, you receive an email confirming your registration and informing you that you can get started selling in the Reserved Instance Marketplace. ## Bank account for disbursement AWS must have your bank information in order to disburse funds collected when you sell your Reserved Instance. The bank you specify must have a US address. For more information, see [Additional seller requirements for paid products](https://docs.aws.amazon.com/marketplace/latest/userguide/user-guide-for-sellers.html#additional-seller-requirements-for-paid-products) in the *AWS Marketplace Seller Guide*. **To register a default bank account for disbursements** 1. Open the [Reserved Instance Marketplace Seller Registration](https://us-east-1.console.aws.amazon.com/rimarketplace/home?region=us-east-1) page and sign in using your AWS credentials. 1. On the **Manage Bank Account** page, provide the following information about the bank through to receive payment: + Bank account holder name + Routing number + Account number + Bank account type **Note** If you are using a corporate bank account, you are prompted to send the information about the bank account via fax (1-206-765-3424). After registration, the bank account provided is set as the default, pending verification with the bank. It can take up to two weeks to verify a new bank account, during which time you can't receive disbursements. For an established account, it usually takes about two days for disbursements to complete. **To change the default bank account for disbursement** 1. On the [Reserved Instance Marketplace Seller Registration](https://us-east-1.console.aws.amazon.com/rimarketplace/home?region=us-east-1) page, sign in with the account that you used when you registered. 1. On the **Manage Bank Account** page, add a new bank account or modify the default bank account as needed. ## Tax information Your sale of Reserved Instances might be subject to a transaction-based tax, such as sales tax or value-added tax. You should check with your business's tax, legal, finance, or accounting department to determine if transaction-based taxes are applicable. You are responsible for collecting and sending the transaction-based taxes to the appropriate tax authority. As part of the seller registration process, you must complete a tax interview in the [Seller Registration Portal](https://portal.aws.amazon.com/ec2/ri/seller_registration?action=taxInterview). The interview collects your tax information and populates an IRS form W-9, W-8BEN, or W-8BEN-E, which is used to determine any necessary tax reporting obligations. The tax information you enter as part of the tax interview might differ depending on whether you operate as an individual or business, and whether you or your business are a US or non-US person or entity. As you fill out the tax interview, keep in mind the following: + Information provided by AWS, including the information in this topic, does not constitute tax, legal, or other professional advice. To find out how the IRS reporting requirements might affect your business, or if you have other questions, contact your tax, legal, or other professional advisor. + To fulfill the IRS reporting requirements as efficiently as possible, answer all questions and enter all information requested during the interview. + Check your answers. Avoid misspellings or entering incorrect tax identification numbers. They can result in an invalidated tax form. Based on your tax interview responses and IRS reporting thresholds, Amazon might file Form 1099-K. Amazon mails a copy of your Form 1099-K on or before January 31 in the year following the year that your tax account reaches the threshold levels. For example, if your account reaches the threshold in 2018, your Form 1099-K is mailed on or before January 31, 2019. For more information about IRS requirements and Form 1099-K, see [Form 1099-K FAQs](https://www.irs.gov/newsroom/form-1099-k-faqs-third-party-filers-of-form-1099-k) on the IRS website. ## Price your Reserved Instances When setting the price for your Reserved Instances, consider the following: + **Upfront price** – The upfront price is the only price that you can specify for the Reserved Instance that you're selling. The upfront price is the one-time price that the buyer pays when they purchase each Reserved Instance. Because the value of Reserved Instances decreases over time, by default, AWS can set prices to decrease in equal increments month over month. However, you can set different upfront prices based on when your reservation sells. For example, if your Reserved Instance has nine months of its term remaining, you can specify the amount that you would accept if a customer were to purchase that Reserved Instance with nine months remaining. You could set another price with five months remaining, and yet another price with one month remaining. The minimum allowed price in the Reserved Instance Marketplace is \$10.00. + **Limits** – The following limits for selling Reserved Instances apply to the *lifetime* of your AWS account. They are not annual limits and they can't be increased. + **You can sell up to \$150,000 in Reserved Instances**. + **You can sell up to 5,000 Reserved Instances**. + **Can't modify** – You cannot modify your listing directly. However, you can change your listing by first canceling it and then creating another listing with new parameters. + **Can cancel** – You can cancel your listing at any time, as long as it's in the `active` state. You cannot cancel the listing if it's already matched or being processed for a sale. If some of the instances in your listing are matched and you cancel the listing, only the remaining unmatched instances are removed from the listing. ## List your Reserved Instances As a registered seller, you can choose to sell one or more of your Reserved Instances. You can choose to sell all of them in one listing or in portions. In addition, you can list Reserved Instances with any configuration of instance type, platform, and scope. The console determines a suggested price. It checks for offerings that match your Reserved Instance and matches the one with the lowest price. Otherwise, it calculates a suggested price based on the cost of the Reserved Instance for its remaining time. If the calculated value is less than \$11.01, the suggested price is \$11.01. If you cancel your listing and a portion of that listing has already been sold, the cancellation is not effective on the portion that has been sold. Only the unsold portion of the listing is no longer available in the Reserved Instance Marketplace. ------ #### [ Console ] **To list a Reserved Instance in the Reserved Instance Marketplace** 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 **Reserved Instances**. 1. Select the Reserved Instances to list, and choose **Actions**, **Sell Reserved Instances**. 1. On the **Configure Your Reserved Instance Listing** page, set the number of instances to sell and the upfront price for the remaining term in the relevant columns. See how the value of your reservation changes over the remainder of the term by selecting the arrow next to the **Months Remaining** column. 1. If you are an advanced user and you want to customize the pricing, you can enter different values for the subsequent months. To return to the default linear price drop, choose **Reset**. 1. Choose **Continue** when you are finished configuring your listing. 1. Confirm the details of your listing, on the **Confirm Your Reserved Instance Listing** page and if you're satisfied, choose **List Reserved Instance**. **To view your listings in 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 **Reserved Instances**. 1. Select the Reserved Instance that you've listed and choose the **My Listings** tab near the bottom of the page. ------ #### [ AWS CLI ] **To manage Reserved Instances in the Reserved Instance Marketplace** 1. Get a list of your Reserved Instances by using the [describe-reserved-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances.html) command. Note that ID of the Reserved Instance that you want to list. 1. Use the [create-reserved-instances-listing](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-reserved-instances-listing.html) command. You must specify the ID of the Reserved Instance, the number of instances, and the pricing schedule. 1. To view your listing, use the [describe-reserved-instances-listings](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances-listings.html) command. 1. To cancel your listing, use the [cancel-reserved-instances-listing](https://docs.aws.amazon.com/cli/latest/reference/ec2/cancel-reserved-instances-listing.html) command. ------ #### [ PowerShell ] **To manage Reserved Instances in the Reserved Instance Marketplace** 1. Get a list of your Reserved Instances by using the [Get-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstance.html) cmdlet. Note that ID of the Reserved Instance that you want to list. 1. Use the [New-EC2ReservedInstancesListing](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2ReservedInstancesListing.html) cmdlet. You must specify the ID of the Reserved Instance, the number of instances, and the pricing schedule. 1. To view your listing, use the [Get-EC2ReservedInstancesListing](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstancesListing.html) cmdlet. 1. To cancel your listing, use the [Stop-EC2ReservedInstancesListing](https://docs.aws.amazon.com/powershell/latest/reference/items/Stop-EC2ReservedInstancesListing.html) cmdlet. ------ ## Reserved Instance listing states **Listing State** on the **My Listings** tab of the Reserved Instances page displays the current status of your listings: The information displayed by **Listing State** is about the status of your listing in the Reserved Instance Marketplace. It is different from the status information that is displayed by the **State** column in the **Reserved Instances** page. This **State** information is about your reservation. + **active**—The listing is available for purchase. + **canceled**—The listing is canceled and isn't available for purchase in the Reserved Instance Marketplace. + **closed**—The Reserved Instance is not listed. A Reserved Instance might be `closed` because the sale of the listing was completed. ## Lifecycle of a listing When all the instances in your listing are matched and sold, the **My Listings** tab shows that the **Total instance count** matches the count listed under **Sold**. Also, there are no **Available** instances left for your listing, and its **Status** is `closed`. When only a portion of your listing is sold, AWS retires the Reserved Instances in the listing and creates the number of Reserved Instances equal to the Reserved Instances remaining in the count. So, the listing ID and the listing that it represents, which now has fewer reservations for sale, is still active. Any future sales of Reserved Instances in this listing are processed this way. When all the Reserved Instances in the listing are sold, AWS marks the listing as `closed`. For example, you create a listing *Reserved Instances listing ID 5ec28771-05ff-4b9b-aa31-9e57dexample* with a listing count of 5. The **My Listings** tab in the **Reserved Instance** console page displays the listing this way: *Reserved Instance listing ID 5ec28771-05ff-4b9b-aa31-9e57dexample* + Total reservation count = 5 + Sold = 0 + Available = 5 + Status = active A buyer purchases two of the reservations, which leaves a count of three reservations still available for sale. Because of this partial sale, AWS creates a new reservation with a count of three to represent the remaining reservations that are still for sale. This is how your listing looks in the **My Listings** tab: *Reserved Instance listing ID 5ec28771-05ff-4b9b-aa31-9e57dexample* + Total reservation count = 5 + Sold = 2 + Available = 3 + Status = active If you cancel your listing and a portion of that listing has already sold, the cancelation is not effective on the portion that has been sold. Only the unsold portion of the listing is no longer available in the Reserved Instance Marketplace. ## After your Reserved Instance is sold When your Reserved Instance is sold, AWS sends you an email notification. Each day that there is any kind of activity, you receive one email notification capturing all the activities of the day. Activities can include when you create or sell a listing, or when AWS sends funds to your account. ------ #### [ Console ] **To track the status of a Reserved Instance listing** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation page, choose **Reserved Instances**. 1. On the **My Listings** tab, find the value of **Listing State**. The tab also contains information about the term, listing price, and a breakdown of how many instances in the listing are available, pending, sold, and canceled. ------ #### [ AWS CLI ] **To track the status of a Reserved Instance listing** Use the [describe-reserved-instances-listings](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances-listings.html) command with the appropriate filter to obtain information about your listings. ``` aws ec2 describe-reserved-instances-listings ``` ------ #### [ PowerShell ] **To track the status of a Reserved Instance listing** Use the [Get-EC2ReservedInstancesListing](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstancesListing.html) cmdlet. ``` Get-EC2ReservedInstancesListing ``` ------ ## Getting paid As soon as AWS receives funds from the buyer, a message is sent to the registered owner account email for the sold Reserved Instance. AWS sends an Automated Clearing House (ACH) wire transfer to your specified bank account. Typically, this transfer occurs between one to three days after your Reserved Instance has been sold. Disbursements take place once a day. You will receive an email with a disbursement report after the funds are released. Keep in mind that you can't receive disbursements until AWS receives verification from your bank. This can take up to two weeks. The Reserved Instance that you sold continues to appear when you describe your Reserved Instances. You receive a cash disbursement for your Reserved Instances through a wire transfer directly into your bank account. AWS charges a service fee of 12 percent of the total upfront price of each Reserved Instance you sell in the Reserved Instance Marketplace. ## Information shared with the buyer When you sell in the Reserved Instance Marketplace, AWS shares your company’s legal name on the buyer’s statement in accordance with US regulations. In addition, if the buyer calls Support because the buyer needs to contact you for an invoice or for some other tax-related reason, AWS might need to provide the buyer with your email address so that the buyer can contact you directly. For similar reasons, the buyer's ZIP code and country information are provided to the seller in the disbursement report. As a seller, you might need this information to accompany any necessary transaction taxes that you remit to the government (such as sales tax and value-added tax). AWS cannot offer tax advice, but if your tax specialist determines that you need specific additional information, [contact Support](https://aws.amazon.com/contact-us/). # Modify Reserved Instances When your needs change, you can modify your Standard or Convertible Reserved Instances and continue to benefit from the billing benefit. You can modify attributes such as the Availability Zone, instance size (within the same instance family and generation), and scope of your Reserved Instance. **Note** You can also exchange a Convertible Reserved Instance for another Convertible Reserved Instance with a different configuration. For more information, see [Exchange Convertible Reserved Instances](ri-convertible-exchange.md). You can modify all or a subset of your Reserved Instances. You can separate your original Reserved Instances into two or more new Reserved Instances. For example, if you have a reservation for 10 instances in `us-east-1a` and decide to move 5 instances to `us-east-1b`, the modification request results in two new reservations: one for 5 instances in `us-east-1a` and the other for 5 instances in `us-east-1b`. You can also *merge* two or more Reserved Instances into a single Reserved Instance. For example, if you have four `t2.small` Reserved Instances of one instance each, you can merge them to create one `t2.large` Reserved Instance. For more information, see [Support for modifying instance sizes](#ri-modification-instancemove). After modification, the benefit of the Reserved Instances is applied only to instances that match the new parameters. For example, if you change the Availability Zone of a reservation, the capacity reservation and pricing benefits are automatically applied to instance usage in the new Availability Zone. Instances that no longer match the new parameters are charged at the On-Demand rate, unless your account has other applicable reservations. If your modification request succeeds: + The modified reservation becomes effective immediately and the pricing benefit is applied to the new instances beginning at the hour of the modification request. For example, if you successfully modify your reservations at 9:15PM, the pricing benefit transfers to your new instance at 9:00PM. You can get the effective date of the modified Reserved Instances by using the [describe-reserved-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances.html) command. + The original reservation is retired. Its end date is the start date of the new reservation, and the end date of the new reservation is the same as the end date of the original Reserved Instance. If you modify a three-year reservation that had 16 months left in its term, the resulting modified reservation is a 16-month reservation with the same end date as the original one. + The modified reservation lists a \$10 fixed price and not the fixed price of the original reservation. + The fixed price of the modified reservation does not affect the discount pricing tier calculations applied to your account, which are based on the fixed price of the original reservation. If your modification request fails, your Reserved Instances maintain their original configuration, and are immediately available for another modification request. There is no fee for modification, and you do not receive any new bills or invoices. You can modify your reservations as frequently as you like, but you cannot change or cancel a pending modification request after you submit it. After the modification has completed successfully, you can submit another modification request to roll back any changes you made, if needed. **Topics** + [ ## Requirements and restrictions for modification ](#ri-modification-limits) + [ ## Support for modifying instance sizes ](#ri-modification-instancemove) + [ ## Submit modification requests ](#ri-modification-process) + [ ## Troubleshoot modification requests ](#ri-modification-process-messages) ## Requirements and restrictions for modification You can modify these attributes as follows. | Modifiable attribute | Supported platforms | Limitations and considerations | | --- | --- | --- | | Change **Availability Zones** within the same Region | Linux and Windows | - | | Change the **scope** from Availability Zone to Region and vice versa | Linux and Windows | A zonal Reserved Instance is scoped to an Availability Zone and reserves capacity in that Availability Zone. If you change the scope from Availability Zone to Region (in other words, from zonal to regional), you lose the capacity reservation benefit. A regional Reserved Instance is scoped to a Region. Your Reserved Instance discount can apply to instances running in any Availability Zone in that Region. Furthermore, the Reserved Instance discount applies to instance usage across all sizes in the selected instance family. If you change the scope from Region to Availability Zone (in other words, from regional to zonal), you lose Availability Zone flexibility and instance size flexibility (if applicable). For more information, see [How Reserved Instance discounts are applied](apply_ri.md). | | Change the **instance size** within the same instance family and generation | Linux/UNIX only Instance size flexibility is not available for Reserved Instances on the other platforms, which include Linux with SQL Server Standard, Linux with SQL Server Web, Linux with SQL Server Enterprise, Red Hat Enterprise Linux, SUSE Linux, Windows, Windows with SQL Standard, Windows with SQL Server Enterprise, and Windows with SQL Server Web. | The reservation must use default tenancy. Some instance families are not supported, because there are no other sizes available. For more information, see [Support for modifying instance sizes](#ri-modification-instancemove) | **Requirements** Amazon EC2 processes your modification request if there is sufficient capacity for your new configuration (if applicable), and if the following conditions are met: + The Reserved Instance cannot be modified before or at the same time that you purchase it + The Reserved Instance must be active + There cannot be a pending modification request + The Reserved Instance is not listed in the Reserved Instance Marketplace + There must be a match between the instance size footprint of the original reservation and the new configuration. For more information, see [Support for modifying instance sizes](#ri-modification-instancemove). + The original Reserved Instances are all Standard Reserved Instances or all Convertible Reserved Instances, not some of each type + The original Reserved Instances must expire within the same hour, if they are Standard Reserved Instances + For modifying instance size, the Reserved Instance must support instance size flexibility. For the list of Reserved Instances that don't support instance size flexibility, see [Instance size flexibility](apply_ri.md#ri-instance-size-flexibility). ## Support for modifying instance sizes You can modify the instance size of a Reserved Instance if the following requirements are met. **Requirements** + The platform is Linux/UNIX. + You must select another instance size in the same [instance family](https://docs.aws.amazon.com/ec2/latest/instancetypes/instance-type-names.html) (indicated by a letter, for example, T) and [generation](https://docs.aws.amazon.com/ec2/latest/instancetypes/instance-type-names.html) (indicated by a number, for example, 2). For example, you can modify a Reserved Instance from `t2.small` to `t2.large` because they're both in the same T2 family and generation. But you can't modify a Reserved Instance from T2 to M2 or from T2 to T3, because in both these examples, the target instance family and generation are not the same as the original Reserved Instance. + You can modify the instance size of a Reserved Instance only if it supports instance size flexibility. For the list of Reserved Instances that don't support instance size flexibility, see [Instance size flexibility](apply_ri.md#ri-instance-size-flexibility). + You can't modify the instance size of Reserved Instances for `t1.micro` instances, because `t1.micro` has only one size. + The original and new Reserved Instance must have the same instance size footprint. **Topics** + [ ### Instance size footprint ](#ri-modification-instance-size-footprint) + [ ### Normalization factors for bare metal instances ](#ri-normalization-factor-bare-metal-2) ### Instance size footprint Each Reserved Instance has an *instance size footprint*, which is determined by the normalization factor of the instance size and the number of instances in the reservation. When you modify the instance sizes in an Reserved Instance, the footprint of the new configuration must match that of the original configuration, otherwise the modification request is not processed. To calculate the instance size footprint of a Reserved Instance, multiply the number of instances by the normalization factor. In the Amazon EC2 console, the normalization factor is measured in units. The following table describes the normalization factor for the instance sizes in an instance family. For example, `t2.medium` has a normalization factor of 2, so a reservation for four `t2.medium` instances has a footprint of 8 units. | Instance size | Normalization factor | | --- | --- | | nano | 0.25 | | micro | 0.5 | | small | 1 | | medium | 2 | | large | 4 | | xlarge | 8 | | 2xlarge | 16 | | 3xlarge | 24 | | 4xlarge | 32 | | 6xlarge | 48 | | 8xlarge | 64 | | 9xlarge | 72 | | 10xlarge | 80 | | 12xlarge | 96 | | 16xlarge | 128 | | 18xlarge | 144 | | 24xlarge | 192 | | 32xlarge | 256 | | 48xlarge | 384 | | 56xlarge | 448 | | 112xlarge | 896 | You can allocate your reservations into different instance sizes across the same instance family as long as the instance size footprint of your reservation remains the same. For example, you can divide a reservation for one `t2.large` (1 @ 4 units) instance into four `t2.small` (4 @ 1 unit) instances. Similarly, you can combine a reservation for four `t2.small` instances into one `t2.large` instance. However, you cannot change your reservation for two `t2.small` instances into one `t2.large` instance because the footprint of the new reservation (4 units) is larger than the footprint of the original reservation (2 units). In the following example, you have a reservation with two `t2.micro` instances (1 unit) and a reservation with one `t2.small` instance (1 unit). If you merge both of these reservations to a single reservation with one `t2.medium` instance (2 units), the footprint of the new reservation equals the footprint of the combined reservations. ![\[Modifying Reserved Instances.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-modify-merge.png) You can also modify a reservation to divide it into two or more reservations. In the following example, you have a reservation with a `t2.medium` instance (2 units). You can divide the reservation into two reservations, one with two `t2.nano` instances (.5 units) and the other with three `t2.micro` instances (1.5 units). ![\[Modifying Reserved Instances.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-modify-divide.png) ### Normalization factors for bare metal instances You can modify a reservation with `metal` instances using other sizes within the same instance family. Similarly, you can modify a reservation with instances other than bare metal instances using the `metal` size within the same instance family. Generally, a bare metal instance is the same size as the largest available instance size within the same instance family. For example, an `i3.metal` instance is the same size as an `i3.16xlarge` instance, so they have the same normalization factor. The following table describes the normalization factor for the bare metal instance sizes in the instance families that have bare metal instances. The normalization factor for `metal` instances depends on the instance family, unlike the other instance sizes. | Instance size | Normalization factor | | --- | --- | | a1.metal | 32 | | m5zn.metal \$1 x2iezn.metal z1d.metal | 96 | | c6g.metal \$1 c6gd.metal \$1 i3.metal \$1 m6g.metal \$1 m6gd.metal \$1 r6g.metal \$1 r6gd.metal \$1 x2gd.metal | 128 | | c5n.metal | 144 | | c5.metal \$1 c5d.metal \$1 i3en.metal \$1 m5.metal \$1 m5d.metal \$1 m5dn.metal \$1 m5n.metal \$1 r5.metal \$1 r5b.metal \$1 r5d.metal \$1 r5dn.metal \$1 r5n.metal | 192 | | c6i.metal \$1 c6id.metal \$1 m6i.metal \$1 m6id.metal \$1 r6d.metal \$1 r6id.metal | 256 | | u-18tb1.metal \$1 u-24tb1.metal | 448 | | u-6tb1.metal \$1 u-9tb1.metal \$1 u-12tb1.metal | 896 | For example, an `i3.metal` instance has a normalization factor of 128. If you purchase an `i3.metal` default tenancy Amazon Linux/Unix Reserved Instance, you can divide the reservation as follows: + An `i3.16xlarge` is the same size as an `i3.metal` instance, so its normalization factor is 128 (128/1). The reservation for one `i3.metal` instance can be modified into one `i3.16xlarge` instance. + An `i3.8xlarge` is half the size of an `i3.metal` instance, so its normalization factor is 64 (128/2). The reservation for one `i3.metal` instance can be divided into two `i3.8xlarge` instances. + An `i3.4xlarge` is a quarter the size of an `i3.metal` instance, so its normalization factor is 32 (128/4). The reservation for one `i3.metal` instance can be divided into four `i3.4xlarge` instances. ## Submit modification requests Before you modify your Reserved Instances, ensure that you have read the applicable [restrictions](#ri-modification-limits). Before you modify the instance size, calculate the total [instance size footprint](#ri-modification-instancemove) of the original reservations that you want to modify and ensure that it matches the total instance size footprint of your new configurations. ------ #### [ Console ] **To modify your Reserved Instances** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. On the **Reserved Instances** page, select one or more Reserved Instances to modify, and choose **Actions**, **Modify Reserved Instances**. If your Reserved Instances are not in the active state or cannot be modified, **Modify Reserved Instances** is disabled. 1. The first entry in the modification table displays attributes of the selected Reserved Instances, and at least one target configuration beneath it. The **Units** column displays the total instance size footprint. Choose **Add** for each new configuration to add. Modify the attributes as needed for each configuration. + **Scope**: Choose whether the configuration applies to an Availability Zone or to the whole Region. + **Availability Zone**: Choose the required Availability Zone. Not applicable for regional Reserved Instances. + **Instance type**: Select the required instance type. The combined configurations must equal the instance size footprint of your original configurations. + **Count**: Specify the number of instances. To split the Reserved Instances into multiple configurations, reduce the count, choose **Add**, and specify a count for the additional configuration. For example, if you have a single configuration with a count of 10, you can change its count to 6 and add a configuration with a count of 4. This process retires the original Reserved Instance after the new Reserved Instances are activated. 1. Choose **Continue**. 1. To confirm your modification choices when you finish specifying your target configurations, choose **Submit modifications**. 1. You can determine the status of your modification request by looking at the **State** column in the Reserved Instances screen. The following are the possible states. + **active* (pending modification)*** — Transition state for original Reserved Instances + **retired* (pending modification)*** — Transition state for original Reserved Instances while new Reserved Instances are being created + **retired** — Reserved Instances successfully modified and replaced + **active** — One of the following: + New Reserved Instances created from a successful modification request + Original Reserved Instances after a failed modification request ------ #### [ AWS CLI ] **To modify your Reserved Instances** Use the [modify-reserved-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-reserved-instances.html) command. You can provide the configuration details in a JSON file. ``` aws ec2 modify-reserved-instances \ --reserved-instances-ids b847fa93-e282-4f55-b59a-1342f5bd7c02 \ --target-configurations file://configuration.json ``` **To get the status of your modification request** Use the [describe-reserved-instances-modifications](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances-modifications.html) command. The status is `processing`, `fulfilled`, or `failed`. ``` aws ec2 describe-reserved-instances-modifications \ --reserved-instances-modification-ids rimod-d3ed4335-b1d3-4de6-ab31-0f13aaf46687 \ --query ReservedInstancesModifications[].Status ``` ------ #### [ PowerShell ] **To modify your Reserved Instances** Use the [Edit-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2ReservedInstance.html) cmdlet. You can provide the configuration details in an object of type `Amazon.EC2.Model.ReservedInstancesConfiguration`. ``` Edit-EC2ReservedInstance ` -ReservedInstancesId b847fa93-e282-4f55-b59a-1342f5bd7c02 ` -TargetConfiguration $configuration ``` **To get the status of your modification request** Use the [Get-EC2ReservedInstancesModification](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstancesModification.html) cmdlet. The status is `processing`, `fulfilled`, or `failed`. ``` Get-EC2ReservedInstancesModification ` -ReservedInstancesModificationId rimod-d3ed4335-b1d3-4de6-ab31-0f13aaf46687 | ` Select Status ``` ------ ## Troubleshoot modification requests If the target configuration settings that you requested were unique, you receive a message that your request is being processed. At this point, Amazon EC2 has only determined that the parameters of your modification request are valid. Your modification request can still fail during processing due to unavailable capacity. In some situations, you might get a message indicating incomplete or failed modification requests instead of a confirmation. Use the information in such messages as a starting point for resubmitting another modification request. Ensure that you have read the applicable [restrictions](#ri-modification-limits) before submitting the request. **Not all selected Reserved Instances can be processed for modification** Amazon EC2 identifies and lists the Reserved Instances that cannot be modified. If you receive a message like this, go to the **Reserved Instances** page in the Amazon EC2 console and check the information for the Reserved Instances. **Error in processing your modification request** You submitted one or more Reserved Instances for modification and none of your requests can be processed. Depending on the number of reservations you are modifying, you can get different versions of the message. Amazon EC2 displays the reasons why your request cannot be processed. For example, you might have specified the same target configuration—a combination of Availability Zone and platform—for one or more subsets of the Reserved Instances you are modifying. Try submitting the modification requests again, but ensure that the instance details of the reservations match, and that the target configurations for all subsets being modified are unique. # Exchange Convertible Reserved Instances You can exchange one or more Convertible Reserved Instances for another Convertible Reserved Instance with a different configuration, including instance family, operating system, and tenancy. There are no limits to how many times you perform an exchange, as long as the new Convertible Reserved Instance is of an equal or higher value than the Convertible Reserved Instances that you are exchanging. When you exchange your Convertible Reserved Instance, the number of instances for your current reservation is exchanged for a number of instances that cover the equal or higher value of the configuration of the new Convertible Reserved Instance. Amazon EC2 calculates the number of Reserved Instances that you can receive as a result of the exchange. You can't exchange Standard Reserved Instances, but you can modify them. For more information, see [Modify Reserved Instances](ri-modifying.md) . **Topics** + [ ## Requirements for exchanging Convertible Reserved Instances ](#riconvertible-exchange-limits) + [ ## Calculate Convertible Reserved Instances exchanges ](#riconvertible-exchange-cost) + [ ## Merge Convertible Reserved Instances ](#ri-merge-convertible) + [ ## Exchange a portion of a Convertible Reserved Instance ](#ri-split-convertible) + [ ## Submit exchange requests ](#ri-exchange-process) ## Requirements for exchanging Convertible Reserved Instances If the following conditions are met, Amazon EC2 processes your exchange request. Your Convertible Reserved Instance must be: + Active + Not pending a previous exchange request + Have at least 24 hours remaining before it expires The following rules apply: + Convertible Reserved Instances must be exchanged for other Convertible Reserved Instances currently offered by AWS. + Convertible Reserved Instances are associated with a specific Region, which is fixed for the duration of the reservation's term. You can't exchange a Convertible Reserved Instance for a Convertible Reserved Instance in a different Region. + To exchange a zonal Convertible Reserved Instance, AWS must have enough capacity for the new instance type in the Region. + You can exchange one or more Convertible Reserved Instances at a time for one Convertible Reserved Instance only. + To exchange a portion of a Convertible Reserved Instance, you can modify it into two or more reservations, and then exchange one or more of the reservations for a new Convertible Reserved Instance. For more information, see [Exchange a portion of a Convertible Reserved Instance](#ri-split-convertible). For more information about modifying your Reserved Instances, see [Modify Reserved Instances](ri-modifying.md). + All Upfront Convertible Reserved Instances can be exchanged for Partial Upfront Convertible Reserved Instances, and vice versa. **Note** If the total upfront payment required for the exchange (true-up cost) is less than \$10.00, AWS automatically gives you a quantity of instances in the Convertible Reserved Instance that ensures that true-up cost is \$10.00 or more. **Note** If the total value (upfront price \$1 hourly price \$1 number of remaining hours) of the new Convertible Reserved Instance is less than the total value of the exchanged Convertible Reserved Instance, AWS automatically gives you a quantity of instances in the Convertible Reserved Instance that ensures that the total value is the same or higher than that of the exchanged Convertible Reserved Instance. + To benefit from better pricing, you can exchange a No Upfront Convertible Reserved Instance for an All Upfront or Partial Upfront Convertible Reserved Instance. + You can't exchange All Upfront and Partial Upfront Convertible Reserved Instances for No Upfront Convertible Reserved Instances. + You can exchange a No Upfront Convertible Reserved Instance for another No Upfront Convertible Reserved Instance only if the new Convertible Reserved Instance's hourly price is the same or higher than the exchanged Convertible Reserved Instance's hourly price. **Note** If the total value (hourly price \$1 number of remaining hours) of the new Convertible Reserved Instance is less than the total value of the exchanged Convertible Reserved Instance, AWS automatically gives you a quantity of instances in the Convertible Reserved Instance that ensures that the total value is the same or higher than that of the exchanged Convertible Reserved Instance. + If you exchange multiple Convertible Reserved Instances that have different expiration dates, the expiration date for the new Convertible Reserved Instance is the date that's furthest in the future. + If you exchange a single Convertible Reserved Instance, it must have the same term (1-year or 3-years) as the new Convertible Reserved Instance. If you merge multiple Convertible Reserved Instances with different term lengths, the new Convertible Reserved Instance has a 3-year term. For more information, see [Merge Convertible Reserved Instances](#ri-merge-convertible). + When Amazon EC2 exchanges a Convertible Reserved Instance, it retires the associated reservation, and transfers the end date to the new reservation. After the exchange, Amazon EC2 sets both the end date for the old reservation and the start date for the new reservation equal to the date of the exchange. For example, if you exchange a three-year reservation that had 16 months left in its term, the new reservation is a 16-month reservation with the same end date as the reservation from the Convertible Reserved Instance that you exchanged. ## Calculate Convertible Reserved Instances exchanges Exchanging Convertible Reserved Instances is free. However, you might be required to pay a true-up cost, which is a prorated upfront cost of the difference between the Convertible Reserved Instances that you had and the new Convertible Reserved Instances that you receive from the exchange. Each Convertible Reserved Instance has a list value. This list value is compared to the list value of the Convertible Reserved Instances that you want in order to determine how many instance reservations you can receive from the exchange. For example: You have 1 x \$135-list value Convertible Reserved Instance that you want to exchange for a new instance type with a list value of \$110. ``` $35/$10 = 3.5 ``` You can exchange your Convertible Reserved Instance for three \$110 Convertible Reserved Instances. It's not possible to purchase half reservations; therefore you must purchase an additional Convertible Reserved Instance to cover the remainder: ``` 3.5 = 3 whole Convertible Reserved Instances + 1 additional Convertible Reserved Instance ``` The fourth Convertible Reserved Instance has the same end date as the other three. If you are exchanging Partial or All Upfront Convertible Reserved Instances, you pay the true-up cost for the fourth reservation. If the remaining upfront cost of your Convertible Reserved Instances is \$1500, and the new reservation would normally cost \$1600 on a prorated basis, you are charged \$1100. ``` $600 prorated upfront cost of new reservations - $500 remaining upfront cost of old reservations = $100 difference ``` ## Merge Convertible Reserved Instances If you merge two or more Convertible Reserved Instances, the term of the new Convertible Reserved Instance must be the same as the old Convertible Reserved Instances, or the highest of the Convertible Reserved Instances. The expiration date for the new Convertible Reserved Instance is the expiration date that's furthest in the future. For example, you have the following Convertible Reserved Instances in your account: | Reserved Instance ID | Term | Expiration date | | --- | --- | --- | | aaaa1111 | 1-year | 2018-12-31 | | bbbb2222 | 1-year | 2018-07-31 | | cccc3333 | 3-year | 2018-06-30 | | dddd4444 | 3-year | 2019-12-31 | + You can merge `aaaa1111` and `bbbb2222` and exchange them for a 1-year Convertible Reserved Instance. You cannot exchange them for a 3-year Convertible Reserved Instance. The expiration date of the new Convertible Reserved Instance is 2018-12-31. + You can merge `bbbb2222` and `cccc3333` and exchange them for a 3-year Convertible Reserved Instance. You cannot exchange them for a 1-year Convertible Reserved Instance. The expiration date of the new Convertible Reserved Instance is 2018-07-31. + You can merge `cccc3333` and `dddd4444` and exchange them for a 3-year Convertible Reserved Instance. You cannot exchange them for a 1-year Convertible Reserved Instance. The expiration date of the new Convertible Reserved Instance is 2019-12-31. ## Exchange a portion of a Convertible Reserved Instance You can use the modification process to split your Convertible Reserved Instance into smaller reservations, and then exchange one or more of the new reservations for a new Convertible Reserved Instance. The following examples demonstrate how you can do this. **Example: Convertible Reserved Instance with multiple instances** In this example, you have a `t2.micro` Convertible Reserved Instance with four instances in the reservation. To exchange two `t2.micro` instances for an `m4.xlarge` instance: 1. Modify the `t2.micro` Convertible Reserved Instance by splitting it into two `t2.micro` Convertible Reserved Instances with two instances each. 1. Exchange one of the new `t2.micro` Convertible Reserved Instances for an `m4.xlarge` Convertible Reserved Instance. ![\[Modifying and exchange Reserved Instances.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-split-cri-multiple.png) **Example: Convertible Reserved Instance with a single instance** In this example, you have a `t2.large` Convertible Reserved Instance. To change it to a smaller `t2.medium` instance and a `m3.medium` instance: 1. Modify the `t2.large` Convertible Reserved Instance by splitting it into two `t2.medium` Convertible Reserved Instances. A single `t2.large` instance has the same instance size footprint as two `t2.medium` instances. 1. Exchange one of the new `t2.medium` Convertible Reserved Instances for an `m3.medium` Convertible Reserved Instance. ![\[Modify and exchange Reserved Instances.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-split-cri-single.png) For more information, see [Support for modifying instance sizes](ri-modifying.md#ri-modification-instancemove) and [Submit exchange requests](#ri-exchange-process). ## Submit exchange requests You can exchange your Convertible Reserved Instances. Reserved Instances that are exchanged are retired. ------ #### [ Console ] **To exchange Convertible Reserved Instances** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. Choose **Reserved Instances**, select the Convertible Reserved Instances to exchange, and choose **Actions**, **Exchange Reserved Instance**. 1. Select the attributes of the desired configuration, and choose **Find offering**. 1. Select a new Convertible Reserved Instance. At the bottom of the screen, you can view the number of Reserved Instances that you receive for the exchange, and any additional costs. 1. When you have selected a Convertible Reserved Instance that meets your needs, choose **Review**. 1. Choose **Exchange**, and then **Close**. ------ #### [ AWS CLI ] **To exchange a Convertible Reserved Instance** 1. Find a new Convertible Reserved Instance that meets your needs by using the [describe-reserved-instances-offerings](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances-offerings.html) command. 1. Get a quote for the exchange by using the [get-reserved-instances-exchange-quote](https://docs.aws.amazon.com/cli/latest/reference/ec2/get-reserved-instances-exchange-quote.html) command. This includes the number of Reserved Instances you get from the exchange, and the true-up cost for the exchange: 1. Perform the exchange by using the [accept-reserved-instances-exchange-quote](https://docs.aws.amazon.com/cli/latest/reference/ec2/accept-reserved-instances-exchange-quote.html) command. ------ #### [ PowerShell ] **To exchange a Convertible Reserved Instance** 1. Find a new Convertible Reserved Instance that meets your needs by using the [Get-EC2ReservedInstancesOffering](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstancesOffering.html) cmdlet. 1. Get a quote for the exchange by using the [GetEC2-ReservedInstancesExchangeQuote](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstancesExchangeQuote.html) cmdlet. This includes the number of Reserved Instances you get from the exchange, and the true-up cost for the exchange: 1. Perform the exchange by using the [Approve-EC2ReservedInstancesExchangeQuote](https://docs.aws.amazon.com/powershell/latest/reference/items/Approve-EC2ReservedInstancesExchangeQuote.html) cmdlet ------ # Reserved Instance quotas You can purchase new Reserved Instances each month. The number of new Reserved Instances that you can purchase each month is determined by your monthly quota, as follows: **** | Quota description | Default quota | | --- | --- | | New [regional](apply_ri.md#apply-regional-ri) Reserved Instances | 20 per Region per month | | New [zonal](apply_ri.md#apply-zonal-ri) Reserved Instances | 20 per Availability Zone per month | For example, in a Region with three Availability Zones, the default quota is 80 new Reserved Instances per month, calculated as follows: + 20 regional Reserved Instances for the Region + Plus 60 zonal Reserved Instances (20 for each of the three Availability Zones) Instances in the `running` state count toward your quota. Instances that are in the `pending`, `stopping`, `stopped`, and `hibernated` states do not count towards your quota. ## View the number of Reserved Instances you have purchased The number of Reserved Instances that you purchase is indicated by the **Instance count** field (console) or the `InstanceCount` parameter (AWS CLI). When you purchase new Reserved Instances, the quota is measured against the total instance count. For example, if you purchase a single Reserved Instance configuration with an instance count of 10, the purchase counts towards your quota as 10, not 1. You can view how many Reserved Instances you have purchased by using the Amazon EC2 or the AWS CLI. ------ #### [ Console ] **To view the number of Reserved Instances you have purchased** 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 **Reserved Instances**. 1. Select a Reserved Instance configuration from the table, and check the **Instance count** field. In the following screenshot, the selected line represents a single Reserved Instance configuration for a `t3.micro` instance type. The **Instance count** column in the table view and the **Instance count** field in the detail view (outlined in the screenshot) indicate that there are 10 Reserved Instances for this configuration. ![\[This image shows the Reserved Instances screen in the Amazon EC2 console. The Instance count field is outlined in the screenshot.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-instance-count.png) ------ #### [ AWS CLI ] **To view the number of Reserved Instances you have purchased** Use the [ describe-reserved-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances.html) command and specify the ID of the Reserved Instance configuration. ``` aws ec2 describe-reserved-instances \ --reserved-instances-ids a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 \ --output table ``` The following is example output. The `InstanceCount` field indicates that there are 10 Reserved Instances for this configuration. ``` ------------------------------------------------------------------- | DescribeReservedInstances | +-----------------------------------------------------------------+ || ReservedInstances || |+----------------------+----------------------------------------+| || CurrencyCode | USD || || Duration | 31536000 || || End | 2023-08-27T13:29:44+00:00 || || FixedPrice | 59.0 || || InstanceCount | 10 || || InstanceTenancy | default || || InstanceType | t3.micro || || OfferingClass | standard || || OfferingType | All Upfront || || ProductDescription | Linux/UNIX || || ReservedInstancesId | a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 || || Scope | Region || || Start | 2022-08-27T13:29:45.938000+00:00 || || State | active || || UsagePrice | 0.0 || |+----------------------+----------------------------------------+| ||| RecurringCharges ||| ||+----------------------------------+--------------------------+|| ||| Amount | 0.0 ||| ||| Frequency | Hourly ||| ||+----------------------------------+--------------------------+|| ``` ------ #### [ PowerShell ] **To view the number of Reserved Instances you have purchased** Use the [ Get-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstance.html) Cmdlet and specify the ID of the Reserved Instance configuration. ``` Get-EC2ReservedInstance -ReservedInstancesId a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 ``` The following is example output. The `InstanceCount` field indicates that there are 10 Reserved Instances for this configuration. ``` AvailabilityZone : CurrencyCode : USD Duration : 31536000 End : 1/12/2017 8:57:08 PM FixedPrice : 0 InstanceCount : 10 InstanceTenancy : default InstanceType : t3.medium OfferingClass : standard OfferingType : All Upfront ProductDescription : Windows RecurringCharges : {} ReservedInstancesId : a1b2c3d4-5678-90ab-cdef-EXAMPLE11111 Scope : Region Start : 10/12/2016 4:00:00 PM State : active Tags : {} UsagePrice : 0 ``` ------ ## Considerations A regional Reserved Instance applies a discount to a running On-Demand Instance. The default On-Demand Instance limit is 20. You cannot exceed your running On-Demand Instance limit by purchasing regional Reserved Instances. For example, if you already have 20 running On-Demand Instances, and you purchase 20 regional Reserved Instances, the 20 regional Reserved Instances are used to apply a discount to the 20 running On-Demand Instances. If you purchase more regional Reserved Instances, you will not be able to launch more instances because you have reached your On-Demand Instance limit. Before purchasing regional Reserved Instances, make sure your On-Demand Instance limit matches or exceeds the number of regional Reserved Instances you intend to own. If required, make sure you request an increase to your On-Demand Instance limit *before* purchasing more regional Reserved Instances. A zonal Reserved Instance—a Reserved Instance that is purchased for a specific Availability Zone—provides a capacity reservation as well as a discount. You *can exceed* your running On-Demand Instance limit by purchasing zonal Reserved Instances. For example, if you already have 20 running On-Demand Instances, and you purchase 20 zonal Reserved Instances, you can launch a further 20 On-Demand Instances that match the specifications of your zonal Reserved Instances, giving you a total of 40 running instances. ## View your Reserved Instance quotas and request a quota increase The Amazon EC2 console provides quota information. You can also request an increase in your quotas. For more information, see [View your current quotas](ec2-resource-limits.md#view-limits) and [Request an increase](ec2-resource-limits.md#request-increase).