> For the complete documentation index, see [llms.txt](https://docs.idea-hpc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idea-hpc.com/best-practices/budget/review-your-aws-spend.md).
# Review your AWS spend
### AWS Cost Explorer
Any EC2 resource launched by IDEA comes with an extensive list of EC2 tags that can be used to get detailed information about your cluster usage. List includes (but not limited to):
* Project Name
* Job Owner
* Job Name
* Job Queue
* Job Id
IDEA automatically assign tags. Custom tags can be added as needed
{% hint style="info" %}
All IDEA generated tags are prefixed with "**idea:**"
{% endhint %}
#### Step1: Enable Cost Allocation Tags
Click on your account name (top right on the screen) then click "**Billing Dashboard**". Once connected to your Billing dashboard, click "**Cost Allocation Tags**" on the left sidebar.
Search all "**idea**" tags then click "Activate". Status of each tag should now be changed to "Active".
Activate all tags to be usable on Cost Explorer
#### Step 2: Query Cost Explorer
{% hint style="info" %}
It could take up to 24 hours for the tags to be visible on Cost Explorer.
{% endhint %}
Access "**AWS Cost Explorer**" service via the EC2 console the click "**Cost Explorer**" on the left sidebar.
Open your Cost Explorer tab and specify your filters. In this example I want to get the EC2 cost (1), group by day for my queue named "cpus" (2).
To get more detailed information, select 'Group By' and apply additional filters. Here is an example if I want user level information for "cpus" queue Click "Tag" section under "Group By" horizontal label (1) and select "idea:JobOwner" tag. Your graph will automatically be updated with a cost breakdown by users for "cpus" queue
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.idea-hpc.com/best-practices/budget/review-your-aws-spend.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.