I purchased a Reserved Instance, but I’m not getting the billing benefit of the Reserved Instance, and the Reserved Instance is displayed as retired. Why is that?

Reserved Instances appear as retired in the Billing and Cost Management console for one of the following reasons:

  • The Reserved Instance term has expired. A reservation covers a particular instance configuration for a one-year or three-year term. After the term expires, you no longer receive the billing benefit or capacity reservation, and the Reserved Instance is marked retired in the console.
  • The upfront charge for the Reserved Instance wasn’t processed successfully, and a new billing period has begun. If the upfront charge for a Reserved Instance wasn’t processed successfully, it remains in the payment-pending state until the charge is retried successfully. If a charge is in the payment-pending state and a new billing period begins, the Reserved Instance moves to the retired state, and the upfront charge can’t be retried.
  • The Reserved Instance was modified. When a Reserved Instance is modified, the old Reserved Instance is marked as retired in the console.

Reserved Instances in the retired state can’t be activated, but you can purchase a new Reserved Instance of the same configuration.

Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-04-08

Updated: 2017-06-06