> 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/leaving-pumps-aws-organization.md).

# Leaving Pump's AWS Organization

You can request a 30-day notice to disconnect from Pump at any time. There are no contracts or lock-in periods. This page covers what happens when you leave and how the process works.

> **Note:** If your offboarding involves a Consent to Assign (CTA) process, it can only be processed during a specific window each month (typically between the 10th and 20th, though the exact dates vary). Contact your Pump account team to confirm the current window.

### What happens when you leave

| Area                 | What happens                                                                                                                                                                  |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Existing commitments | Reserved Instances and Savings Plans that Pump purchased remain in your AWS account. They run off naturally on their original expiration schedule. Nothing is canceled early. |
| Billing              | Your billing relationship reverts to direct. You pay AWS instead of Pump.                                                                                                     |
| Cloud resources      | All your AWS resources, configurations, and data remain exactly as they are. Pump never modifies infrastructure.                                                              |
| IAM roles            | You can delete the Pump IAM roles (read-only, Autopilot, Pump Secure, Pump Infra) from your account at any time after disconnecting.                                          |
| Pump dashboards      | Your historical cost data in Pump's dashboards is no longer accessible after disconnection. Download any reports you need before offboarding.                                 |
| SSO                  | If Pump migrated your SSO during onboarding, you will need to migrate it back to your own org or set up a new IAM Identity Center instance. Coordinate with the Pump team.    |

### How to leave

1. Contact Pump support at <support@pump.co> or your Account Manager.
2. The Pump team coordinates the transition, including:
   * Removing your account from Pump's AWS Organization
   * Your account becomes standalone and responsible for its own billing
   * Ensuring any active commitment renewals are handled appropriately
3. Once your account is standalone, you can optionally create your own AWS Organization or join another one.

### Leaving a previous org to join Pump

If you are joining Pump and need to leave your current AWS Organization first, the process is:

1. Log in to the AWS Console.
2. Click your account name in the top-right corner and select **Organization**.
3. Scroll to the bottom of the page and click **Leave organization**.
4. Confirm. Your account becomes standalone and responsible for its own billing.
5. As a standalone account, you can now join Pump through the standard onboarding flow.

This process only applies to member accounts leaving an existing org. If you are the management account of an org, see the Multi-Account Setup page for the correct path.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.pump.co/aws/leaving-pumps-aws-organization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.