Configuring credentials in AWS - Quick Revision & Summary

Recall & Review

beginner

What is the purpose of AWS credentials?

AWS credentials are used to prove your identity to AWS services so you can securely access and manage your cloud resources.

beginner

Where can AWS credentials be stored for CLI use?

AWS credentials can be stored in the ~/.aws/credentials file or set as environment variables on your computer.

beginner

What are the two main parts of AWS credentials?

The two main parts are the Access Key ID and the Secret Access Key. The Access Key ID is like a username, and the Secret Access Key is like a password.

beginner

Why should you never share your AWS Secret Access Key?

Because it grants full access to your AWS resources, sharing it risks unauthorized use and potential data loss or charges.

intermediate

What AWS tool helps you manage credentials securely and rotate them regularly?

AWS Identity and Access Management (IAM) helps you create, manage, and rotate credentials securely.

Which file typically stores AWS CLI credentials on your computer?

A ~/.aws/keys

B ~/.aws/credentials

C /etc/aws/credentials

D ~/.aws/config

The ~/.aws/credentials file is the default location for storing AWS CLI credentials.

What are the two components of AWS credentials?

A Access Key ID and Secret Access Key

B Username and Password

C API Token and Password

D Access Token and Refresh Token

AWS credentials consist of an Access Key ID and a Secret Access Key.

Why is it important to rotate AWS credentials regularly?

A To reduce AWS billing costs

B To increase AWS service speed

C To improve security by limiting exposure if credentials are compromised

D To enable multi-factor authentication

Regular rotation reduces risk if credentials are leaked or stolen.

Which AWS service helps you manage users and their credentials securely?

A IAM

B S3

C EC2

D CloudWatch

IAM (Identity and Access Management) manages users, groups, and credentials.

How can you provide AWS credentials to an application running on an EC2 instance securely?

A Send credentials via email

B Hardcode credentials in the application code

C Store credentials in a public GitHub repo

D Use IAM roles assigned to the EC2 instance

IAM roles assigned to EC2 instances provide temporary credentials securely without hardcoding.

Explain how AWS credentials are configured for CLI use and why this is important.

Think about where the CLI looks for credentials and why protecting them matters.

Describe best practices for managing AWS credentials to keep your cloud resources safe.

Consider how to reduce risk of unauthorized access.

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