> 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/sign-in-and-security/govcloud-access.md).

# Do I Need to Grant Access to My GovCloud Account?

## How It Works Without Direct GovCloud Access

Because AWS requires that every GovCloud account is associated with a commercial AWS payer account and the cost & usage data is passed back to that payer account, if Archera's IAM role is installed on the **commercial payer account** associated with your GovCloud account, it will be able to pull and process cost visibility data to enable platform features like:

* Scenario planning/forecasting
* Cost attribution/monitoring
* Cloud inventory

...all **without any direct access to your GovCloud environment**.

## Optional Direct GovCloud Access

To enable certain Archera features in your GovCloud environment — such as:

* Automated commitment management
* Detailed commitment visibility
* Resource optimization recommendations

...you will be required to grant Archera's GovCloud account IAM access to your GovCloud environment.

## Access is Optional

Granting this additional access is optional. The platform will work for many use-cases (cost reporting, EDP planning, etc.) without Archera needing direct IAM access to your GovCloud environment. However, some key features like commitment optimization will not be available without this access.

## Related Resources

* [What is the Archera AWS account ID?](/help-center/aws-onboarding/aws-account-id.md) (includes GovCloud account IDs)
* [Do Guaranteed Commitments work with AWS GovCloud?](/help-center/guaranteed-commitments/govcloud.md)
* [How Does Archera Access my AWS Environment?](/help-center/sign-in-and-security/aws-access.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/sign-in-and-security/govcloud-access.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.