Secrets Manager for credentials in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does AWS Secrets Manager rotate credentials automatically?

A developer wants AWS Secrets Manager to automatically rotate database credentials every 30 days. Which mechanism enables this automatic rotation?

A By configuring a Lambda rotation function linked to the secret that updates credentials on schedule

B By manually updating the secret value every 30 days in the console

C By enabling automatic rotation in IAM user settings

D By setting a CloudWatch alarm to notify when credentials expire

💡 Hint

Think about how AWS Secrets Manager can run code to update credentials without manual intervention.

AWS Secrets Manager uses Lambda functions to perform automatic rotation. You link a Lambda rotation function to the secret, and Secrets Manager runs it on the schedule you set to update credentials securely.

❓ security

intermediate

Which IAM policy grants least privilege to read a specific secret?

You want to allow an application to read only one secret named prod/db-password from AWS Secrets Manager. Which IAM policy snippet grants the least privilege?

A {"Effect":"Allow","Action":"secretsmanager:GetSecretValue","Resource":"*"}

B {"Effect":"Allow","Action":"secretsmanager:GetSecretValue","Resource":"arn:aws:secretsmanager:region:account-id:secret:prod/db-password-*"}

C {"Effect":"Allow","Action":"secretsmanager:*","Resource":"*"}

D {"Effect":"Allow","Action":["secretsmanager:GetSecretValue","secretsmanager:DescribeSecret"],"Resource":"arn:aws:secretsmanager:region:account-id:secret:prod/db-password-*"}

💡 Hint

Least privilege means only needed actions on only the specific secret.

Option D allows only the necessary actions to read and describe the specific secret resource. Other options are either too broad or allow all actions.

❓ Architecture

advanced

Designing secure access to secrets for multiple microservices

You have multiple microservices running on AWS ECS that need access to different secrets stored in AWS Secrets Manager. What is the best architecture to securely provide each microservice access only to its required secrets?

A Create one IAM role per microservice with permissions scoped to only its secrets, and assign the role to the ECS task

B Store all secrets in one secret and share it with all microservices

C Use a single IAM role for all microservices with permissions to all secrets

D Embed secrets directly in the container images for each microservice

💡 Hint

Think about isolating permissions per microservice to follow security best practices.

Assigning one IAM role per microservice with scoped permissions ensures each service can only access its own secrets, reducing risk if one service is compromised.

❓ Configuration

advanced

What is the correct AWS CLI command to retrieve a secret value?

You want to retrieve the plaintext value of a secret named prod/api-key using AWS CLI. Which command will return only the secret string?

A aws secretsmanager get-secret-value --secret-id prod/api-key

B aws secretsmanager describe-secret --secret-id prod/api-key

C aws secretsmanager get-secret-value --secret-id prod/api-key --query SecretString --output text

D aws secretsmanager list-secrets --filters Key=name,Values=prod/api-key

💡 Hint

Focus on extracting only the secret string, not metadata.

The command in option C uses --query to extract only the SecretString field and outputs it as plain text, which is the secret value.

✅ Best Practice

expert

Ensuring secure secret access in a multi-account AWS environment

Your company uses multiple AWS accounts for development, testing, and production. You want to centralize secret management in one account but allow secure read access to secrets from other accounts. What is the best practice to achieve this?

A Use AWS S3 buckets with public read access to store secrets

B Use resource-based policies on secrets in the central account to allow cross-account IAM roles from other accounts to access secrets

C Share IAM users across accounts with the same credentials

D Copy secrets manually to each account and manage them separately

💡 Hint

Think about how AWS Secrets Manager supports cross-account access securely.

Resource-based policies on secrets allow you to grant cross-account access securely without duplicating secrets or sharing credentials. This is the recommended best practice.

Practice

1. What is the main purpose of AWS Secrets Manager?

easy

A. To securely store and manage sensitive information like passwords and keys

B. To host websites and web applications

C. To monitor network traffic and logs

D. To provide virtual machines for computing

Solution

1. Step 1: Understand Secrets Manager's role

   AWS Secrets Manager is designed to keep sensitive data like passwords and API keys safe and separate from application code.

2. Step 2: Compare options to this role

   Options B, C, and D describe other AWS services or functions unrelated to Secrets Manager.

3. Final Answer:

   To securely store and manage sensitive information like passwords and keys -> Option A

4. Quick Check:

   Secrets Manager = Secure storage for secrets [OK]

Hint: Secrets Manager = safe place for passwords and keys [OK]

Common Mistakes:

• Confusing Secrets Manager with hosting or monitoring services
• Thinking it manages virtual machines
• Assuming it stores non-sensitive data

2. Which of the following is the correct AWS CLI command to retrieve a secret value from Secrets Manager?

easy

A. aws secrets get-value --secret MySecret

B. aws secretsmanager fetch-secret --id MySecret

C. aws secretsmanager get-secret-value --secret-id MySecret

D. aws secretmanager retrieve --name MySecret

Solution

1. Step 1: Recall the correct AWS CLI syntax for Secrets Manager

   The official command to get a secret's value is 'aws secretsmanager get-secret-value' with the '--secret-id' parameter.

2. Step 2: Check each option's correctness

   Options A, B, and C use incorrect commands or parameters that do not exist in AWS CLI.

3. Final Answer:

   aws secretsmanager get-secret-value --secret-id MySecret -> Option C

4. Quick Check:

   Correct CLI command = aws secretsmanager get-secret-value --secret-id MySecret [OK]

Hint: Remember 'get-secret-value' with '--secret-id' for retrieval [OK]

Common Mistakes:

• Using wrong command verbs like fetch or retrieve
• Mixing up parameter names
• Assuming 'secretmanager' is spelled differently

3. Given this Python code snippet using boto3 to get a secret, what will be printed if the secret exists and contains JSON with key 'password'?

import boto3
import json
client = boto3.client('secretsmanager')
response = client.get_secret_value(SecretId='MySecret')
secret = json.loads(response['SecretString'])
print(secret['password'])

medium

A. The entire JSON string without parsing

B. The password string stored in the secret

C. An error because 'SecretString' is missing

D. None, because the secret is not decoded

Solution

1. Step 1: Understand the boto3 get_secret_value response

   The response contains 'SecretString' which holds the secret as a JSON string. The code parses it with json.loads.

2. Step 2: Access the 'password' key from parsed JSON

   After parsing, secret['password'] accesses the password value stored in the secret, which is printed.

3. Final Answer:

   The password string stored in the secret -> Option B

4. Quick Check:

   Parsed JSON secret prints password value [OK]

Hint: Parse 'SecretString' JSON then access keys [OK]

Common Mistakes:

• Trying to print 'SecretString' without parsing
• Assuming 'SecretBinary' is used here
• Not loading JSON before accessing keys

4. You wrote this code to get a secret but get a KeyError: 'SecretString'. What is the likely cause?

response = client.get_secret_value(SecretId='MySecret')
print(response['SecretString'])

medium

A. The secret ID is incorrect

B. The secret is empty and has no keys

C. The client is not authenticated

D. The secret is stored as binary, so 'SecretString' key is missing

Solution

1. Step 1: Understand the response keys from get_secret_value

   If the secret is stored as binary, the response contains 'SecretBinary' instead of 'SecretString'. Accessing 'SecretString' causes KeyError.

2. Step 2: Identify cause of KeyError

   The error means 'SecretString' key is missing, likely because the secret is binary, not string.

3. Final Answer:

   The secret is stored as binary, so 'SecretString' key is missing -> Option D

4. Quick Check:

   Binary secret = no 'SecretString' key [OK]

Hint: Check if secret is binary; then use 'SecretBinary' key [OK]

Common Mistakes:

• Assuming secret is always a string
• Ignoring authentication errors
• Thinking secret ID typo causes KeyError

5. You want your application to automatically rotate database credentials stored in Secrets Manager every 30 days. Which approach is best to achieve this securely and with minimal manual work?

hard

A. Enable Secrets Manager automatic rotation with a Lambda function that updates the database credentials

B. Manually update the secret value in Secrets Manager every 30 days

C. Store credentials in environment variables and update them manually

D. Use a cron job on the application server to change database passwords and update Secrets Manager

Solution

1. Step 1: Understand Secrets Manager rotation feature

   Secrets Manager supports automatic rotation using Lambda functions to update credentials securely without manual intervention.

2. Step 2: Compare options for automation and security

   Enable Secrets Manager automatic rotation with a Lambda function that updates the database credentials uses built-in rotation with Lambda, which is secure and automatic. Options B, C, and D require manual steps or insecure practices.

3. Final Answer:

   Enable Secrets Manager automatic rotation with a Lambda function that updates the database credentials -> Option A

4. Quick Check:

   Automatic rotation with Lambda = best practice [OK]

Hint: Use Secrets Manager rotation with Lambda for auto updates [OK]

Common Mistakes:

• Relying on manual updates risking stale credentials
• Storing secrets insecurely in environment variables
• Using external cron jobs instead of built-in rotation