- AWS CLI (>= 1.15.49)
The initial setup of your credentials will require you to use your root
account. It's the login you initially signed up for AWS with. You can then create a set of initial root
credentials once using the AWS Web Console, which in turn allow you to create a set of lower-privilege credentials you can then use to further provision your account.
Note: You should never use your root
account credentials outside of provisioning other, lower-tier IAM-level privileged users and access credentials. Your root
account is the one and only entrypoint into your AWS account, its credentials are uncurtailed and should never exist beyond a short, purpose-driven amount of time!
- Log into your AWS account using the AWS Web Console and navigate to the dropdown on the top right corner with your email address or the name you gave the account on it
- Select "My Security Credentials"
- Discard the warning screen by clicking on "Continue to Security Credentials", we will only be doing this once and removing the access credentials afterwards
- Select "Access keys (access key ID and secret access key)"
- Select "Create new access key"
- Click on "Show Access Key"
- Note down both of the values and close the overlay.
Set up a profile for the root credentials with the AWS CLI:
$ aws configure --profile root-account
Note: You can call your profile by any name that you want, it doesn't have to be root-account
. Just make sure the following code examples are adjusted accordingly where root-account
is used as an identifier.
For the AWS Access Key ID
and AWS Secret Access Key
use the values you've just written down. The default region can be any region you prefer. You need to specify them with their "Region code" (i.e. eu-central-1
or us-east-1
). The output format doesn't matter.
To test your access you can run:
$ AWS_PROFILE="root-account" aws --region eu-central-1 ec2 describe-instances
{
"Reservations": []
}
An empty list ([]
) is a valid response since you haven't commissioned any resources yet.
You can now continue with the any of the scenarios of the kickstarter.
Make sure to remove the Security Credentials you created earlier from you root account afterwards!. Even if you should need them again in the future you should invalidate/delete them now and create new credentials (and run through the above process once more) when you want to provision you're done.
Once you have provisioned users with sufficient privileges to manage your account (the iam_one_account
or iam_two_accounts
are examples for this) you should delete the Security Credentials in your root
account again:
- Log into your AWS account using the AWS Web Console and your email address you signed up with AWS for and navigate to the dropdown on the top right corner with your email address or the name you gave the account on it
- Select "My Security Credentials"
- Discard the warning screen by clicking on "Continue to Security Credentials"
- Select "Access keys (access key ID and secret access key)"
- Click on "[x]" on the right hand side in the table where it shows your available credentials
- Confirm the "Delete Access Key" modal with "Yes"
- Repeat the prior step for any Access Key that might have been added to your
root
account