Using AWS Organizations, a solutions architect from the management account used the IAM user Support1 to create a new member account with email finance1@example.com. What is the recommended method to create IAM users in that newly created member account?

The correct method is to assume the OrganizationAccountAccessRole from the management account. This role is automatically created in new member accounts by AWS Organizations and grants administrative access, allowing the creation of IAM users and other resources without needing to use the root user credentials directly. This is a security best practice, as it avoids using the root user. Using the root user credentials (first and third options) is strongly discouraged for daily tasks due to the extensive permissions of the root user. The initial 64-character password is for the root user and should be used only for initial setup or critical account recovery. Attempting to sign in with the management account's root password and the new member account's email (third option) will fail because these are distinct accounts. Signing in with the new member account ID and the Support1 IAM credentials (fourth option) will also fail because Support1 is an IAM user in the management account, not the new member account, and does not have direct access to the new member account without assuming a role.