Configuring credentials in AWS - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the AWS credentials file path.

AWS

aws configure set [1] ~/.aws/credentials

Drag options to blanks, or click blank then click option'

Acredential_file

Bprofile

Ccredentials_file

Dconfig_file

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to set the credentials file path using 'aws configure set', which is not supported.

The config_file option is used to specify the path to the AWS config file, while the credentials file path is not set using 'aws configure set'. The AWS CLI does not support setting the credentials file path via 'aws configure set'.

2fill in blank

medium

Complete the command to set the AWS access key ID.

AWS

aws configure set aws_access_key_id [1]

Drag options to blanks, or click blank then click option'

AAKIAIOSFODNN7EXAMPLE

Baccess_key

Cmy-secret-key

D1234567890

Attempts:

3 left

💡 Hint

Common Mistakes

Using the secret access key instead of the access key ID.

Using a placeholder like 'my-secret-key' instead of the actual key.

The AWS access key ID is a specific alphanumeric string like AKIAIOSFODNN7EXAMPLE.

3fill in blank

hard

Fix the error in the AWS CLI command to set the default region.

AWS

aws configure set region [1]

Drag options to blanks, or click blank then click option'

Auswest2

Bus-west-2

Cus-west_2

Dus-west2

Attempts:

3 left

💡 Hint

Common Mistakes

Removing hyphens or replacing them with underscores.

Using region names without proper formatting.

The correct AWS region format uses hyphens, like us-west-2.

4fill in blank

hard

Fill both blanks to configure a named profile with access key and secret key.

AWS

aws configure set aws_access_key_id [1] --profile [2]

Drag options to blanks, or click blank then click option'

AAKIAIOSFODNN7EXAMPLE

Bdefault

Cmyprofile

DwJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the access key and profile name.

Using 'default' when a named profile is required.

Use the access key ID for the first blank and the profile name for the second blank.

5fill in blank

hard

Fill all three blanks to configure AWS CLI with profile, region, and output format.

AWS

aws configure set region [1] --profile [2]
aws configure set output [3] --profile [2]

Drag options to blanks, or click blank then click option'

Ajson

Bus-east-1

Cdevprofile

Dtable

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong region format.

Confusing output format options.

Not repeating the profile name in both commands.

Set the region to us-east-1, profile to devprofile, and output format to json.

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