Hey everyone! I'm looking to move a standalone AWS account into a new organization, and I've never done this before, so I want to make sure I cover all the bases. The new organization uses Service Control Policies (SCPs), and even though I won't assign any to the new Organizational Unit (OU), the account will inherit policies from the root. I'm especially looking for insights on a few topics:
- SCPs: Are there tools that can help analyze CloudTrail logs to figure out potential issues with the SCPs that may affect the account?
- Tags: Are there any implications since new tags will apply when it's added to the organization?
- Billing: What changes in billing occur? Will they stop charging my card, especially since this setup includes consolidated billing?
- Support considerations.
- AWS Marketplace private offerings.
- Reserved instances and savings plans.
If anyone has experience with this transition, I'd love your advice and insights! Thanks in advance!
4 Answers
Just a heads up, if your account is new enough to still have Free Tier credits, moving it to an organization will instantly expire those credits.
Don't forget about stack sets! They can be really useful in this context. Also, check out the AWS Account Assessment tool. It might help you navigate this process better.
Thanks! I didn't know about the AWS Account Assessment tool. I’ll definitely check it out.
I've worked with AWS governance for a lot of accounts, so here's the scoop: Account inheritance is a big deal in AWS Organizations. Even in your new OU, you’ll be under the influence of higher-level policies. Make sure to consult with your governance team about this. Billing typically goes to the payer account, and you'll still have access to Cost Explorer for details. As for reserved instances and savings plans, that's a discussion you need to have with your financial operations team.
Be ready for some complexities based on the current setup of your standalone account and the guidelines of the new organization. The transition can be smooth or it could lead to major disruptions. For more complicated scenarios, consider migrating resources in phases. Just a note, this transition can't fully be captured by Terraform yet, which could lead to additional issues down the line.
Got it, I'm hoping it’s a straightforward move without too many hiccups. I’m not looking to migrate resources, just a straight move to the new OU.
Thanks for the heads-up! Luckily, no Free Tier for me, but I appreciate it.