> 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/faq/aws-account-owner-verification.md).

# Purchase Blocked by AWS Account Owner Verification

If a submitted plan shows as **Blocked** and the check reads `AccountOwnerNotVerifiedException`, the email address on your AWS Organization's management account has not been verified. AWS requires this before it will accept changes to the organization, so the purchase waits until it is done.

## How to resolve it

The owner of the management account email does this. It takes a few minutes.

1. Sign in to your AWS Organization's **management account**.
2. Open **AWS Organizations**, then **Settings**.
3. Under the management account email, click **Resend email verification**.
4. Open the verification email from AWS and complete the verification.

Archera retries the purchase automatically. No action is needed in Archera.

AWS documents the requirement here: [Email verification with AWS Organizations](https://docs.aws.amazon.com/organizations/latest/userguide/about-email-verification.html).

## Not the same as adjusting account ownership

This is about verifying your own management account's email. It does not involve changing the email on any Archera account. If you are preparing for a PPA/EDP and need to take ownership of Archera's Guaranteed Commitment accounts, that is a separate process: see [Adjusting Ownership of Guaranteed Commitment Account on AWS](/help-center/faq/adjust-commitment-ownership.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/faq/aws-account-owner-verification.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.