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.