> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/aws/onboarding/join-account-s-leave-own-aws-org.md).
# Join Account(s) - leave own AWS org
### Path 1: Join Account(s)
This path is recommended if you do not have SSO configured for your AWS Organization and do not have cross-account communication dependencies (shared logging, centralized security, cross-account IAM roles).
An AWS account can only belong to one Organization at a time. To join Pump's Organization, you first dissolve your existing one.
#### Steps
1. Log in to the AWS Console using your management account.
2. Navigate to **Organizations > Settings**.
3. Click **Delete organization**.
4. All member accounts become standalone accounts.
5. For each standalone account, follow the standard Pump onboarding flow (deploy the CloudFormation stack, authorize Pump as billing partner).
To add multiple standalone accounts to Pump, navigate to **Settings > Integrations > New Account** in the Pump dashboard and deploy a CloudFormation stack for each account.
#### What to evaluate before dissolving your org
Dissolving an AWS Organization affects several services. Review each before proceeding.
| Area | Impact |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Access control | If you have SSO configured through AWS IAM Identity Center, dissolving the org will disrupt SSO access. Do not use this path if SSO is active. |
| Cross-account logging | Centralized CloudTrail, AWS Config, or security logging may stop working if they depend on the org structure. |
| Service Control Policies (SCPs) | All SCPs are removed when the org is dissolved. Any access restrictions enforced by SCPs will no longer apply. |
| Consolidated billing | Member accounts begin accruing charges independently until they join Pump's org. |
| Organizational Units (OUs) | OU structure is lost. Pump can recreate your OU structure within its org if needed. |
If any of these apply to your environment, use Path 2 instead.
---
# 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://help.pump.co/aws/onboarding/join-account-s-leave-own-aws-org.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.
