Pump
Back to Home
  • Getting Started
    • Introduction
    • The Hitchhiker's Guide to Pump
    • Joining Pump
      • Our Features
      • Running your Savings Estimate
      • Selecting a mode (Autopilot or Manual Mode)
      • Savings Survey
      • When can I expect to see Savings?
      • Money Back Guarantee
    • Billing Info
      • Billing Process
      • First Month Billing
      • Currencies Supported
      • Supported Payment Methods
      • Invoice Verification or Errors
      • Invoices for Indian Customers
      • Invoices from AWS
      • Sales Tax or Value Added Tax (VAT)
    • How Pump works
    • Real Customers, Real Success Stories
    • Money Back Guarantee
    • FAQ
  • AWS: Joining Pump
    • How to Join Pump (3 easy steps)
      • Step 1 - View Estimate
      • Step 2 - Authorize Pump
      • Step 3 - Know your business
      • Finishing Touches
        • Inviting your team
        • Adding additional AWS accounts
        • Post onboarding
        • AWS Seller Registration
        • Sign up for Auto Pay
    • AWS Multi-account architecture
      • via 'Join Account(s)'
      • via 'Join With A Pre-Existing Org(s)'
      • Join via CTA
      • How Pump handles SSO
      • Leave an AWS Organization
    • AWS Role Deployment and Permissions
  • Maximizing Pump with AWS
    • Using Pump
      • Savings Summary
      • Past Savings
      • Reserved Instances
      • Savings Plans
      • Group buying discounts
      • Payments
      • Sales or Value added tax (VAT)
      • Credit FAQ
    • AWS Discount Prices
    • Pump Secure
    • AWS Credits FAQ
  • GCP: Joining Pump
    • Getting Started with GCP
      • Step 1 - View Savings Estimate
      • Step 2 - Authorize Pump
  • Azure: Joining Pump
    • Azure Role Deployment and Permissions
  • Pump University
    • Welcome to Pump University
  • Support
    • Fast & Free Support
    • Security & Access
      • Cross Account Role
      • Role Deployment
      • Access Management
      • Other Housekeeping
    • Invoices from AWS
    • Invoices from GCP
    • Request a Demo
    • Security Standards
    • Changing Infrastructure while on Pump
Powered by GitBook
On this page
  1. AWS: Joining Pump

AWS Multi-account architecture

PreviousSign up for Auto PayNextvia 'Join Account(s)'

Last updated 1 month ago

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 and seeing which account is designated as 'management account'

Once you've checked your savings with your management account, following the steps listed in , 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

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 support@pump.co 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.

Organizational structure

If you have only one account within your AWS organization (like the example shown above) or have only one active account amongst other unused accounts and don't have SSO setup - we recommend you disassociating your accounts from the organization & join the standalone account via the steps linked

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 article to see how Pump handles SSO!

Learn more about the set up!

Your organizational structure is important, and Pump can help maintain it without disruption. If needed, we can recreate your existing 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

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
steps.
here.
this
'billing group'
OUs (Organizational Units)
link
Getting started