> 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-onboarding/test-in-subaccount.md). # Can I Test Archera in an AWS Sub-Account? Yes — you can add Archera's Read-only IAM credential to any AWS sub-account that has at minimum access to Cost Explorer, and optionally with the ability to generate a Cost & Usage Report. ## Full Platform Access This will enable you to access the full Archera platform; however, much of the data around commitment coverage, savings, and net spend will be incorrect until you install Archera's Read-only IAM credential to the **master account** in that organization. ## Exception: Fully Functional Sub-Account Only Install The only exception that would allow a sub-account-only install to be fully functional is if: * The sub-account is responsible for its own RI & SP purchasing * It is not part of an EDP/PPA organization * AWS organization discount sharing is turned off ## What You Can Test with Sub-Account Only * Scenario analysis * Cost visibility & alerting * Right-sizing planning * Preview of commitment purchasing & renewal tools ## Limitations You will **not** be able to move forward with: * Commitment automation * Custom cost reporting * Guaranteed Reserved Instances ## Related Resources * [How Does Archera Access my AWS Environment?](/help-center/sign-in-and-security/aws-access.md) * [What IAM permissions does the Archera AWS Read-only deployment require?](/help-center/aws-onboarding/iam-permissions-trial.md) * [What is the Archera AWS account ID?](/help-center/aws-onboarding/aws-account-id.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-onboarding/test-in-subaccount.md?ask=&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.