Multi-Account Management Using AWS Organizations

Posted by vipul on February 11th, 2021

The AWS organization offers policy management from multiple AWS Accounts. Users can create a group of accounts and then apply policies to those groups that centrally control the use of AWS Services down to the API level across multiple accounts. This helps you to centrally manage the accounts without the need for custom scripts and manual processes. This new AWS service includes consolidated billing and account management capabilities which help you to better manage the security and compliance requirements of your business.

Association: It addresses an element that you make by consolidating a bunch of AWS accounts. All these part accounts are overseen inside the association.

Root: The parent holder that holds all the records solidified in an association. The root client account is consequently made by AWS when you make an association.

Association Unit: Acts like a holder for accounts inside a root. An Association Unit(OU) can likewise contain other Association Units, empowering you to make a chain of importance. This chain of importance will resemble an upset tree, with a root at the top, the OUs as the branches, and records as the leaves.

Record: An ordinary AWS account that contains all your AWS assets. Clients can make another record or welcome others to join their association. The record that makes the association is known as the expert record while different records are known as part accounts.

Greeting: It is utilized to depict the way toward welcoming another record to join an association. Just an expert record client can give a greeting. The welcomed account turns into a part account once it acknowledges the greeting. Solicitations can likewise be shipped off current individuals when an association needs to change something, for example, empowering all highlights.

Handshake: An interaction including two gatherings (the handshake initiator and the beneficiary) trade data.