AWS Multi-account architecture

If your company has a multi-account architecture, we recommend calculating the savings estimate on Pump first using your management account. This will provide us with a fairly accurate estimate of your potential savings.

Your management account is your 'root account' that you created your AWS account with, you can also verify this by visiting this link and seeing which account is designated as 'management account'

Once you've checked your savings with your management account, following the steps listed in Getting started, assess if you'd need to be breaking your organization or importing it whole.

Otherwise, removing an AWS Org can impact the following ways and we recommend you evaluate each of the impact items for yourself -

Impact
Description

Access control

Transitioning to Pump while keeping your AWS organization intact ensures seamless access control and permissions. If you have SSO set up through AWS Identity Center, we recommend keeping your accounts within the organization for a smooth experience. Our team is here to support you through the process. Check out this article to see how Pump handles SSO!

Cross-account functions management

Maintaining cross-account functions like logging, security, and monitoring is essential for a well-structured cloud environment. If you’re making changes to your organization, we’re here to guide you through best practices and ensure everything runs smoothly. Feel free to reach out to [email protected] or start an intercom chat for personalized assistance!

Account management

Managing multiple accounts efficiently is key to optimizing your AWS experience. With Pump's Billing Group setup, you can simplify your account management while keeping everything organized and streamlined.

Learn more about the 'billing group' set up!

Organizational structure

Your organizational structure is important, and Pump can help maintain it without disruption. If needed, we can recreate your existing OUs (Organizational Units) within our system to ensure your accounts remain structured in a way that works best for you.

Bottom line - If you do not have SSO setup for your AWS organization or have communication setup between accounts, we recommend that you break up your organization following these steps.

However, if you do have it setup or cannot break an organization due to a complex setup, we recommend you to follow the steps here.

Last updated