> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/aws-faq/cost-explorer-increase.md).

# Why Does AWS Cost Explorer Show a Cost Increase After Commitment Purchases?

## Why Does a Commitment Purchase Show as a Big Cost Spike?

No Upfront commitment costs (GRIs, SPs or RIs) can look a bit strange in the **"Unblended Cost"** Cost Explorer view when purchased during a month that is still in progress. AWS attributes the entire cost of the reservation over the month to the day the reservations were purchased and the account that contains those reservations.

For subsequent months, similar behavior will occur where AWS attributes the entire cost of the reservation over the month to the 1st day of the month.

## Understanding Amortized Cost

As the month progresses you will see the cost of those commitments be appropriately "spread out" across the days of usage in the **"Amortized Cost"** view, ultimately resulting in a lower cost for the month as a whole.

The "Amortized Cost" view additionally attributes the costs of commitments to the accounts that are using those commitments rather than the account that contains those commitments.

## Related Resources

* [Why do I see new monthly charges from AWS Cost Explorer after installing Archera?](/help-center/aws-faq/cost-explorer-charges.md)
* [Why Not Just Use AWS Cost Explorer?](/help-center/aws-faq/why-not-cost-explorer.md)


---

# 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://docs.archera.ai/help-center/aws-faq/cost-explorer-increase.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.