To make that association, one downloads an Access Keys file containing tokens for authenticating AWS API calls. Each AWS Profile is associated with either a root account or an IAM account. Where this intersects with the AWS CLI is the concept of the AWS Profile. But the hows and wherefores of doing that is beyond the scope of this particular guide, which is focused on setting up AWS CLI. This lets you assign specific permissions to each IAM account based on the needs of the project. The best practice is to create one or more IAM accounts for each project. Creating an IAM account is handled in the IAM dashboard, but doing so is fairly involved since you must create several things.ĪWS documentation on Identities (Users, Groups and Roles). To create a root account, go to the AWS website and sign up. The IAM account can be thought of as a sub-account, and is created after you create the root account. The root account is what's created when one signs up for an AWS account. In AWS there are two kinds of accounts: The root account, and an IAM account. ![]() Setting up the AWS CLI tool is fairly easy, but there are several considerations to ensuring it is correctly set up. It is recommended that you create an IAM account for each project, for security. To proceed with this guide, you must already have an AWS account. ![]() ![]() In this guide we'll discuss the AWS CLI version 2, which is the latest version at the time of writing.
0 Comments
Leave a Reply. |