Configuring credentials in AWS - Try It Yourself

Configuring AWS Credentials for CLI Access

📖 Scenario: You are setting up your computer to securely access AWS services using the AWS Command Line Interface (CLI). This requires configuring your AWS credentials so the CLI knows who you are and what permissions you have.

🎯 Goal: Configure AWS credentials by creating the necessary files and adding your access keys so you can use AWS CLI commands securely.

📋 What You'll Learn

Create the AWS credentials file with the correct profile and keys

Create the AWS config file with the default region

Use the exact file paths and file names for AWS CLI to recognize

Use the exact profile name default

Use the exact access key ID AKIAEXAMPLE123456

Use the exact secret access key wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

Set the default region to us-east-1

💡 Why This Matters

🌍 Real World

Setting up AWS credentials is essential for developers and administrators to securely access AWS services from their local machines or servers.

💼 Career

Knowing how to configure AWS credentials is a fundamental skill for cloud engineers, DevOps specialists, and anyone working with AWS infrastructure.

1

Create AWS credentials file

Create a file named credentials inside the ~/.aws/ directory. Add a profile named default with the exact access key ID AKIAEXAMPLE123456 and secret access key wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY. Use the exact format shown below:

AWS

# Your code here to create ~/.aws/credentials with the default profile and keys

Hint

Remember the credentials file must have the profile name in square brackets, then the keys on separate lines.

2

Create AWS config file with default region

Create a file named config inside the ~/.aws/ directory. Add a profile named default and set the region to us-east-1 exactly as shown:

AWS

# Your code here to create ~/.aws/config with default region

Hint

The config file uses the profile name in square brackets and the region setting below it.

3

Verify AWS CLI can use the credentials

Write the exact AWS CLI command to check your configured identity using the default profile. Use the command aws sts get-caller-identity --profile default.

AWS

# Your code here to write the AWS CLI command to verify identity

Hint

This command shows your AWS user identity to confirm credentials are working.

4

Set environment variable for AWS profile

Add the exact environment variable AWS_PROFILE and set it to default so AWS CLI uses this profile by default. Use the syntax export AWS_PROFILE=default for Linux/macOS or setx AWS_PROFILE default for Windows.

AWS

# Your code here to set AWS_PROFILE environment variable to default

Hint

Setting this environment variable saves you from typing --profile default every time.

Practice

1. What is the main purpose of AWS credentials?

easy

A. To prove your identity and allow access to AWS services

B. To store your AWS billing information

C. To configure your AWS service regions

D. To monitor AWS service usage

Solution

1. Step 1: Understand what credentials do

   AWS credentials are like a key that proves who you are when you use AWS services.

2. Step 2: Identify the correct purpose

   They allow AWS to know you and give you permission to use services securely.

3. Final Answer:

   To prove your identity and allow access to AWS services -> Option A

4. Quick Check:

   Credentials = Identity proof [OK]

Hint: Credentials prove identity to AWS services [OK]

Common Mistakes:

• Confusing credentials with billing info
• Thinking credentials set regions
• Assuming credentials monitor usage

2. Which file stores AWS access keys for different profiles by default?

easy

A. ~/.aws/config

B. ~/.aws/credentials

C. /etc/aws/keys

D. ~/.aws/access

Solution

1. Step 1: Recall default AWS credential file

   AWS stores access keys in the file named 'credentials' inside the '.aws' folder in your home directory.

2. Step 2: Differentiate from config file

   The 'config' file stores settings like region and output format, not keys.

3. Final Answer:

   ~/.aws/credentials -> Option B

4. Quick Check:

   Access keys = ~/.aws/credentials [OK]

Hint: Access keys live in ~/.aws/credentials file [OK]

Common Mistakes:

• Mixing up config and credentials files
• Using wrong file paths
• Assuming keys are in system folders

3. Given this AWS credentials file snippet:

[default]
aws_access_key_id=AKIA123456
aws_secret_access_key=secret123

[dev]
aws_access_key_id=AKIADEV123
aws_secret_access_key=devsecret456

What happens if you run AWS CLI without specifying a profile?

medium

A. It asks you to enter credentials manually

B. It uses the 'dev' profile credentials

C. It throws an error for missing profile

D. It uses the 'default' profile credentials

Solution

1. Step 1: Identify default profile usage

   When no profile is specified, AWS CLI uses the 'default' profile credentials automatically.

2. Step 2: Check the given profiles

   The file has a 'default' and a 'dev' profile; without specifying, 'default' is chosen.

3. Final Answer:

   It uses the 'default' profile credentials -> Option D

4. Quick Check:

   No profile specified = default used [OK]

Hint: No profile given? AWS CLI uses 'default' [OK]

Common Mistakes:

• Assuming 'dev' is default
• Expecting error without profile
• Thinking manual input is required

4. You try to run AWS CLI commands but get an error: Unable to locate credentials. What is the most likely cause?

medium

A. The AWS region is not set in config

B. The AWS CLI version is outdated

C. The ~/.aws/credentials file is missing or empty

D. Your internet connection is down

Solution

1. Step 1: Understand the error meaning

   'Unable to locate credentials' means AWS CLI cannot find your access keys anywhere.

2. Step 2: Identify common causes

   This usually happens if the credentials file is missing, empty, or incorrectly placed.

3. Final Answer:

   The ~/.aws/credentials file is missing or empty -> Option C

4. Quick Check:

   Missing credentials file = error [OK]

Hint: Check if ~/.aws/credentials file exists and has keys [OK]

Common Mistakes:

• Blaming CLI version for missing credentials
• Confusing region setting with credentials
• Assuming internet issues cause credential errors

5. You want to securely allow an EC2 instance to access S3 without storing access keys on the instance. Which method should you use?

hard

A. Use IAM roles attached to the EC2 instance

B. Hardcode access keys in your application code

C. Store access keys in ~/.aws/credentials on the instance

D. Use environment variables with access keys on the instance

Solution

1. Step 1: Identify secure credential methods

   Storing keys on the instance or in code risks exposure and is not best practice.

2. Step 2: Use IAM roles for EC2

   IAM roles provide temporary credentials automatically and securely to the instance without manual keys.

3. Final Answer:

   Use IAM roles attached to the EC2 instance -> Option A

4. Quick Check:

   EC2 access without keys = IAM roles [OK]

Hint: Use IAM roles for EC2 to avoid storing keys [OK]

Common Mistakes:

• Storing keys on instance files
• Hardcoding keys in code
• Using environment variables insecurely