Configuring credentials in AWS - Practice Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding AWS Credentials Storage

Where does the AWS CLI store credentials by default after running aws configure?

A In environment variables only

B In the AWS S3 bucket named 'aws-credentials'

C In the AWS Management Console under IAM Users

D In the <code>~/.aws/credentials</code> file on the local machine

💡 Hint

Think about where the AWS CLI saves your access keys locally.

The AWS CLI stores credentials in the ~/.aws/credentials file by default. This file contains your access key ID and secret access key for different profiles.

❓ security

intermediate

Identifying Risks of Hardcoding Credentials

What is the main security risk of hardcoding AWS credentials directly in application code?

A Credentials can be accidentally exposed if the code is shared or pushed to public repositories

B The application will run slower due to embedded credentials

C AWS automatically revokes hardcoded credentials after 24 hours

D Hardcoded credentials increase the cost of AWS services

💡 Hint

Think about what happens if someone else sees your code with credentials inside.

Hardcoding credentials risks accidental exposure, especially if the code is shared publicly or with unauthorized users. This can lead to unauthorized access to your AWS resources.

❓ Configuration

advanced

Using Environment Variables for AWS Credentials

Which environment variables must be set to provide AWS credentials for an application without using the AWS CLI configuration files?

A AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

B AWS_PROFILE and AWS_REGION

C AWS_SESSION_TOKEN and AWS_DEFAULT_OUTPUT

D AWS_BUCKET_NAME and AWS_ACCESS_KEY

💡 Hint

Focus on the variables that hold the key ID and secret key.

The environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY provide the access key and secret key directly to applications, bypassing config files.

❓ service_behavior

advanced

Effect of Missing Credentials on AWS SDK Calls

What happens when an AWS SDK call is made without any configured credentials available?

A The SDK automatically creates temporary credentials

B The SDK call succeeds with limited read-only access

C The SDK call fails with an authentication error indicating missing credentials

D The SDK retries indefinitely until credentials are provided

💡 Hint

Think about how AWS protects resources from unauthorized access.

If no credentials are found, AWS SDK calls fail with an authentication error because AWS cannot verify the caller's identity.

❓ Architecture

expert

Best Practice for Managing Credentials in a Multi-Account AWS Environment

In a multi-account AWS setup, what is the best practice to manage credentials securely and efficiently for applications that need access across accounts?

A Use the root account credentials for all applications to simplify access

B Use AWS IAM roles with cross-account trust and assume-role functionality instead of sharing static credentials

C Store all credentials in a shared S3 bucket accessible by all applications

D Create separate IAM users in each account and hardcode their credentials in applications

💡 Hint

Consider how AWS recommends granting temporary access securely between accounts.

Using IAM roles with cross-account trust allows applications to assume roles securely without sharing long-term credentials, following AWS best practices for security and scalability.