> 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/joining-via-cta.md).

# Joining via CTA

Some organizations have security or compliance constraints that require a different onboarding model. In these cases, Pump can onboard your AWS account through a Consent to Assign (CTA) agreement. CTA transfers the ownership and billing of your AWS management account to Pump so Pump can fully manage billing and savings optimization on your behalf.

CTA is offered at Pump's discretion and is not available to all customers.

### When CTA is used

CTA is typically used when:

| Scenario                                                                  | Why CTA fits                                                                                  |
| ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Organizational security policies prevent joining another AWS Organization | CTA transfers management account ownership rather than moving member accounts between orgs    |
| Compliance requirements dictate specific billing ownership structures     | CTA formalizes the billing relationship at the account ownership level                        |
| The standard multi-account onboarding paths are not feasible              | CTA provides an alternative when Path 1 (dissolve org) and Path 2 (import org) cannot be used |

### How the CTA process works

#### Step 1: Discovery

Pump reviews your setup on a discovery call to confirm whether CTA is the right fit.

During this step, you deploy a read-only CloudFormation stack and run a savings estimate to evaluate the potential value of joining Pump. This is the same read-only flow used in standard onboarding.

#### Step 2: CTA agreement

Once you decide to move forward, Pump shares the CTA agreement. As part of this process:

1. You update the root user email address of the AWS management account to a Pump-provided address.
2. Pump updates the billing details of the management account.

#### Step 3: Onboarding

You deploy the Autopilot CloudFormation stack to grant Pump access to billing and savings optimization. This is the same Autopilot role used in standard onboarding.

After the CTA is completed, Pump manages your billing and commitment purchases.

### Distributor discount

After the CTA is completed, your AWS account will show a distributor discount in the AWS Console. This is a standard AWS construct that appears when working with an AWS Partner.

Key details about the distributor discount:

| Detail                   | Explanation                                                                                                                         |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| What it is               | A standard AWS billing line item applied to accounts managed by an AWS Partner                                                      |
| Who receives it          | The discount primarily flows to Ingram Micro (Pump's distribution partner), with a portion flowing back to Pump                     |
| Impact on your pricing   | None. Your pricing, savings, and billing with Pump remain exactly as agreed.                                                        |
| How to read your balance | Exclude the distributor discount line item when comparing your actual costs. The discount does not represent savings passed to you. |

### What does not change

Your infrastructure, workloads, and configurations are unaffected by the CTA process. You retain full control of your AWS resources. The CTA changes billing ownership and management account root credentials only.


---

# 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/onboarding/joining-via-cta.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.