Why is a Reserved Instance showing as "Retired" in the console?

Last updated: 2019-06-19

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

Resolution

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

  • The Reserved Instance term expired. After the term expires, you no longer receive the billing benefit or capacity reservation, and the Reserved Instance is marked as retired in the console.
  • The upfront charge for the Reserved Instance wasn't processed successfully, and a new billing period has started. If the upfront charge for a Reserved Instance isn'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 starts, then 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.
  • You sold the Reserved Instance on the RI Marketplace. After the Reserved Instance is sold, it 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 with the same configuration.


Did this article help you?

Anything we could improve?


Need more help?