> For the complete documentation index, see [llms.txt](https://docs.finopscenter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finopscenter.com/cfm-processes/financial-budget-to-cloud-allocation/account-allocation.md).

# Account Allocation

All AWS Accounts are at minimum allocated to 1 Financial Budget and define as an Account Type (Production, Pre-Production, Shared, Development or Sandbox).  To complete mapping the total allocation must be 100%.

<figure><img src="https://988932576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXbqCrcU65ULbgldtjmvZ%2Fuploads%2FlCDHO6aYRN164m84Wm8S%2Fimage.png?alt=media&amp;token=3887fff0-c967-4a40-b3c5-5b57edbead63" alt=""><figcaption></figcaption></figure>

Accounts can be mapped to multiple budgets but need to have total allocation of 100%.

<figure><img src="https://988932576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXbqCrcU65ULbgldtjmvZ%2Fuploads%2F37tl1LIAyBhPWwiI3UpA%2Fimage.png?alt=media&amp;token=de6c4381-b0aa-4415-940e-1cd485b62104" alt=""><figcaption><p>Account Mapping Multiple Budgets</p></figcaption></figure>

Allocation can be updated to a new start date and allocation

<figure><img src="https://988932576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXbqCrcU65ULbgldtjmvZ%2Fuploads%2FCnGOoTqp3wJEorkYWnvP%2Fimage.png?alt=media&amp;token=bc19cd35-8433-49f7-aa42-b7b559580afe" alt=""><figcaption><p>Current Mapping</p></figcaption></figure>

Select Remap to update account allocation and start date

<figure><img src="https://988932576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXbqCrcU65ULbgldtjmvZ%2Fuploads%2FXxWG84TQsn1ARUwMHvvq%2Fimage.png?alt=media&amp;token=9d3b4449-7f12-4ce7-8e35-d96c9f5fa7d7" alt=""><figcaption><p>Update Allocation</p></figcaption></figure>

New allocation will history of allocations with current in green highlight. Effective dates of allocation are in Effective Column with the timestamp of updates in lower left of table.&#x20;

<figure><img src="https://988932576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXbqCrcU65ULbgldtjmvZ%2Fuploads%2FV7VaD4dEPd8LUmCx7ziG%2Fimage.png?alt=media&amp;token=d3e3ff46-8de0-4c09-8035-4dfc70b4b640" alt=""><figcaption></figcaption></figure>


---

# 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.finopscenter.com/cfm-processes/financial-budget-to-cloud-allocation/account-allocation.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.
