Merging AWS Accounts for Firm_A and Firm_B - Steps for Effective Policy Management

Merging AWS Accounts for Effective Policy Management

Prev Question Next Question

Question

A Media firm Firm_A uses AWS infrastructure and has a global presence for its sports programming & broadcasting network.

It uses AWS Organization to manage multiple AWS accounts.

Recently it was acquired by Firm_B which also uses AWS Infrastructure.

Firm_B also has its own sets of AWS accounts.

After the merger, AWS Accounts of both organizations need to merge to create & manage policies more effectively. As an AWS Consultant, which of the following steps would you suggest to the client to move the master account of the original media firm to the organization used by the merged entity? (Select THREE.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

Correct Answer - A, C, D.

To move the master account from one organization to another organization, the following steps need to be implemented:

· Remove all member accounts from the old organization.

· Delete the old organization.

· Invite the master account of the old organization to be a member account of the new organization.

Option B is incorrect as the master account of an AWS organization cannot be replaced by another member account.

Option E is incorrect as a master account will be joining as a member account of the new organization, not as a master account.

For more information on migrating accounts between AWS organizations, refer to the following URL:

https://aws.amazon.com/premiumsupport/knowledge-center/organizations-move-accounts/

The merger of two organizations with separate AWS accounts requires a consolidation of resources to ensure effective management and administration of the merged infrastructure. To move the master account of the original media firm to the organization used by the merged entity, the following steps need to be taken:

  1. Remove all member accounts from the organization in Firm_A - This is not a recommended step as it will remove all member accounts and the resources associated with them. It will lead to the loss of access to these resources and can cause business disruptions. Therefore, this option is not suitable.

  2. Configure another member account as the master account in the Firm_A organization - This step is also not recommended as it can cause further complications. Configuring another member account as the master account in the Firm_A organization would lead to the loss of all the AWS resources, policies, and account information associated with the original master account. This option is not suitable.

  3. Delete the organization in Firm_A - Deleting the organization in Firm_A is not recommended as it will lead to the loss of all member accounts, AWS resources, policies, and account information associated with the organization. This option is not suitable.

  4. Invite the Firm_A master account to join the new organization (Firm_B) as a member account - This is a recommended step as it allows the Firm_A master account to join the new organization as a member account. Once the account is added to the new organization, all the resources associated with the account will become part of the new organization, and the policies can be managed more effectively.

  5. Invite the Firm_A master account to join the new organization (Firm_B) as a master account - This is also a recommended step as it allows the Firm_A master account to join the new organization as a master account. Once the account is added to the new organization, it can become the master account for the new organization, and all the policies can be managed more effectively.

Therefore, the recommended steps to move the master account of the original media firm to the organization used by the merged entity are to invite the Firm_A master account to join the new organization (Firm_B) as a member or a master account, depending on the needs of the organization.