> 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/multi-account-setup.md).
# Multi-Account Setup
If your company runs multiple AWS accounts within an AWS Organization, setup requires coordination with the Pump team. This page covers the options for connecting multi-account environments to Pump.
### Before you start
Run a savings estimate using your management account first. The management account provides the most complete view of your organization's spend and gives Pump an accurate baseline for savings projections.
To confirm which account is your management account, navigate to **AWS Console > Organizations > Accounts** and look for the account labeled "Management account."
### Choosing your onboarding path
How you connect depends on your current AWS Organization setup. There are three paths.
| Path | Best for | Setup method |
| ------------------------------ | ---------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| **Join Account(s)** | Organizations with a single active account, no SSO, and no cross-account dependencies | Self-serve |
| **Join With Pre-Existing Org** | Organizations with SSO, cross-account logging, or complex multi-account configurations | Assisted setup with a Pump solutions architect |
| **Consent to Assign (CTA)** | Organizations with security or compliance constraints that require a different ownership model | Assisted setup at Pump's discretion |
### 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).
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.
### Path 2: Join With Pre-Existing Org
This path is for organizations with SSO, cross-account configurations, or other dependencies that make dissolving the org impractical.
This is an assisted process. Contact the Pump team by booking a call, sending a message via Slack, or emailing to discuss the setup.
#### How it works
1. Pump provisions a new AWS Organization for your company.
2. Your accounts are moved into the Pump-managed org.
3. You run a Pump-provided script to export your existing organization infrastructure, including SSO configuration (IAM Identity Center), Resource Access Manager (RAM) shares, SCPs, and other org-level policies.
4. You are provided a delegated administrator account within the new org. You run an import script as the delegated admin to restore your org-level configuration.
5. Pump recreates your OU structure within the new org.
#### What you retain
| Access | Details |
| ----------------------- | -------------------------------------------------------- |
| Delegated admin account | Full access to org-level management services |
| Root access | You maintain root access over all of your accounts |
| SSO | Restored via the export/import process (see SSO on Pump) |
### Path 3: Consent to Assign (CTA)
See the dedicated Joining via CTA page for this path.
### Adding accounts after initial setup
Once your initial setup is complete, you can add additional AWS accounts to Pump at any time.
1. Navigate to **Settings > Integrations > New Account** in the Pump dashboard.
2. Deploy a new CloudFormation stack for each account, following the same process as initial onboarding.
Each account requires its own CloudFormation stack and IAM role.
### StackSets for bulk deployment
If you manage many AWS accounts, Pump supports CloudFormation StackSets to deploy the IAM role across multiple accounts in a single operation. This avoids deploying individual stacks per account.
Contact your Pump representative for StackSet configuration. The StackSet deploys the same read-only (and optionally Autopilot) IAM role to every target account in your org.
---
# 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/multi-account-setup.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.
