AWS Authorized Reseller Moving an AWS account to another organization

Moving an AWS Account to Another Organization: The Ultimate Guide

Ah, the AWS universe! A sprawling cosmos of cloud services, where accounts float like planets, and sometimes, you just want to relocate one to a different organization. Whether you're reorganizing your cloud empire, consolidating billing, or just feeling adventurous, moving an AWS account might be on your to-do list. Don't worry—it's not as complicated as assembling IKEA furniture (well, maybe a little). Buckle up, grab your digital toolkit, and let's navigate this cosmic journey together!

Why Would You Want to Move an AWS Account?

Reorganizing Cloud Realms

Sometimes, your AWS accounts are like a cluster of mismatched socks—out of place and in need of sorting. Moving an account allows you to streamline management, delegate permissions more efficiently, or just straighten out your cloud closet.

Billing and Cost Management

Splitting or consolidating billing can be a game-changer. Moving accounts to different organizations helps in tracking costs more accurately, creating budgets, and avoiding the awkwardness of shared bills that look like a mystery novel.

Compliance and Security

Got a new compliance regime or security requirement? Relocating accounts can help isolate sensitive workloads, ensuring you stay on the right side of regulations without turning your entire cloud into a security maze.

Understanding Organizations and Accounts in AWS

Before we dive into the how-to, let's clarify what we're dealing with. An AWS Organization is like a family reunion—everything is under one roof, but each member (account) can have their own quirks.

• Master Account: The big cheese that manages everything.
• Member Accounts: The family members, each with their own settings but under the master’s umbrella.

Moving an account is essentially changing which family the account belongs to, like swapping cousins at the family picnic.

The Step-by-Step Guide to Moving an AWS Account

Pre-Flight Checks: Is Your Account Ready?

1. Ensure the account is not the master account of its current organization.
2. Verify that the account has no ongoing consolidated billing or pending invitations.
3. Backup any critical configurations or data—better safe than sorry, especially if things go awry.

Step 1: Prepare the Destination Organization

AWS Authorized Reseller Log in as an administrator to the destination AWS Organization. Make sure you have the proper permissions because AWS isn't keen on letting just anyone move accounts around willy-nilly.

Step 2: Remove the Account from the Current Organization

This is the delicate bit. You essentially have to disassociate the account from its current organization. To do this:

1. Sign into the AWS account you want to move.
2. Navigate to the AWS Organizations dashboard.
3. Choose the account, then select Remove from Organization.

Warning: Removing an account could temporarily disable some services or cause minor chaos—think of it as a quick layoff, not a catastrophe.

Step 3: Invite the Account to the New Organization

Now, as an admin of the destination organization:

1. Go to the Membership section in AWS Organizations.
2. Click on Invite Account.
3. Enter the account ID or email associated with the account.
4. Send the invitation and wait for the owner to accept.

Step 4: Accept the Invitation and Confirm

Once the account owner receives the invitation, they need to:

1. Log into their AWS account.
2. Navigate to AWS Organizations.
3. Accept the invitation.

Congratulations! Your account is now officially part of the new organization. You may need to adjust permissions, tags, or billing settings depending on your needs.

AWS Authorized Reseller Pitfalls and Gotchas

Don’t Forget Service Quotas

Moving accounts doesn’t update service quotas automatically. Ensure quotas are adequate in the new organization to avoid service disruptions. It’s like moving to a new house—make sure you have enough internet bandwidth and Wi-Fi extenders.

Billing Woes

Check how billing links are set up post-move. Sometimes, moving an account can cause confusion in consolidated billing setups. Double-check billing dashboards to avoid surprise charges (or complaints from your finance team).

Permissions and Role Challenges

Permissions might need a tweak after the move. You might find yourself locked out of certain services or needing to re-establish cross-account roles. Think of it as changing your phone number; inform everyone who needs to reach you.

Post-Move Best Practices

• Review all AWS services to make sure they’re operational.
• Update IAM policies and permissions to reflect the new organization structure.
• Revisit billing configurations to ensure cost tracking is accurate.
• Document the change for audit and future reference—your future self will thank you.

In Conclusion: Moving Made Easy (Well, Nearly)

Moving an AWS account to another organization isn't as daunting as it sounds. With a little prep, patience, and the willingness to face some occasional digital quirks, you can reorganize your cloud management scheme without breaking a sweat. Remember, in the world of cloud computing, flexibility is king—so don’t be afraid to move things around like a cloud-kingpin! Happy migrating!