Home

Account Setup

1. Create a new AWS account underneath your existing AWS Organization
2. Request via AWS Support or your account representative from AWS that they "activate" your account. This can take hours if not, 10+ days to finish activating. This is entirely based on your AWS Account History so if you have an AWS representative, it helps to ask them to "Activate" your account. As they might be able to get it done faster.
3. While you wait on activation you can continue to create your IAM role and IAM User.

• For the IAM user, within your sub account create an IAM user/key with full "Administrator Access".
• For the IAM role, you will need to make it assumable by the IAM User you just created and grant the role full "Administrator Access". Here is a video on how to create the role.

4. Keep track of the IAM user accesskey/secret as well as the IAM Role ARN (Amazon Resource Name) as you will need these 3 values when setting your cluster.

Learn more:

• https://docs.aws.amazon.com/organizations/latest/userguide/orgs_introduction.html
• https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_create.html
• https://repost.aws/knowledge-center/create-and-activate-aws-account
• https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html
• https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html

Environment Variables / AWS Authentication for terraform AWS Provider and AWS CLI

• We recommend creating a .env file with these values for future use but export the following using the IAM user Access Key and Secret from earlier:

export AWS_ACCESS_KEY_ID=XXXXXXXXXXXXXXXXXXXXXX
export AWS_SECRET_ACCESS_KEY=XXXXXXXXXXXXXXXXXXXXXX
export AWS_DEFAULT_REGION=us-west-2

Learn more:

• https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html