> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/aws/using-pump/reserved-instances.md).

# Reserved Instances

### What are Reserved Instances (RIs)?

AWS Reserved Instances are a way to save money on many computing resources on Amazon Web Services (AWS). With RIs, customers can reserve compute capacity for a specific period (typically one or three years) and receive a significant discount on the hourly charge for that instance type. This can result in cost savings of up to 75% compared to on-demand prices. Essentially, RIs enable customers to prepay for computing capacity and in return, receive a lower cost per hour for that capacity. The best part? You can also buy reserved instances that are "no upfront" meaning there isn't a huge charge at the beginning, and instead, you pay a monthly rate to AWS, still at a discount.

### When are RIs billed?

RIs are billed on your account on the 1st of each month at 12am UTC, just like monthly rent, (except you are saving money 🤑). Therefore, if you or our model has purchased RIs, you may see a big spike in your cost explorer at the beginning of each month. 

<figure><img src="https://44033590-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9AjQj4Qn0NOuXDBL27jQ%2Fuploads%2FpCTGJyPYnZOrtcSqEzxq%2Fimage%205.png?alt=media&amp;token=b26ecbb4-c195-4cec-8582-a4b1fbc1e20b" alt=""><figcaption><p>Notice the spikes on the first of each moth? Those are from RI charges. In the month of March this RI is not consumed (hence no Pump savings), and hence Pump sold that RI in the next 30 days. </p></figcaption></figure>

### What happens to the RIs I purchased in the past?

When an account joins a different organization, AWS adjusts the RI billing for the remainder of the month. This is the scenario that occurs when an account joins us. Rest assured that the 1st of the month RI billing is reset, and AWS only bills you for those RIs from the 1st of the month to the day you join Pump. Pump will bill you for the rest of the month.

You can see the RIs purchased by you categorized separately from those bought by Pump.

<figure><img src="https://44033590-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9AjQj4Qn0NOuXDBL27jQ%2Fuploads%2Fj7rXqLBwTRU9HQMxvNc8%2FScreenshot%202023-04-23%20at%2011.40.00%20PM.png?alt=media&amp;token=0c294130-ebc6-4f00-90d3-36e9effd76ae" alt=""><figcaption></figcaption></figure>

### Where can I see my savings from the RIs on AWS console?

To view your savings from Reserved Instances (RIs) on the AWS console, you can use the Cost Explorer tool.&#x20;

1. Sign in to the AWS Management Console > Cost Explorer > RI Coverage tab (on the left hand side)&#x20;
2. Choose the time period you want to view (e.g., last month, last quarter, custom date range).
3. In the "Savings Plans and Reserved Instances" section, you'll see a breakdown of your RI utilization and savings. You can see the number of RI hours used, the effective hourly rate, and the total savings in dollars.

By using the Cost Explorer, you can get a better understanding of how much money you're saving with your RIs and how effectively you're utilizing them. This can help you make informed decisions about future RI purchases and optimize your cloud spending.

Additionally, Pump makes it simple to track RI savings on the Pump app for anyone to directly understand their savings from this category.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.pump.co/aws/using-pump/reserved-instances.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.