Secrets Manager for credentials in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a secret in AWS Secrets Manager using AWS CLI.

AWS

aws secretsmanager create-secret --name MySecret --secret-string [1]

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

A"MySecretValue"

B"secret"

C"MyPassword"

D"{\"username\":\"admin\",\"password\":\"pass123\"}"

Attempts:

3 left

💡 Hint

Common Mistakes

Using plain text without JSON format.

Not escaping quotes inside the JSON string.

The secret-string must be a JSON string containing the credentials, like username and password.

2fill in blank

medium

Complete the code to retrieve the secret value using AWS CLI.

AWS

aws secretsmanager get-secret-value --secret-id MySecret --query [1] --output text

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

A"SecretString"

B"SecretValue"

C"Secret"

D"Value"

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect key names like 'SecretValue' or 'Value'.

Not using --query to extract the secret string.

The key to get the secret string from the response is 'SecretString'.

3fill in blank

hard

Fix the error in the AWS CLI command to update a secret's value.

AWS

aws secretsmanager update-secret --secret-id MySecret --secret-string [1]

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

A"{username:admin,password:newpass}"

B'{"username":"admin","password":"newpass"}'

C"{\"username\":\"admin\",\"password\":\"newpass\"}"

D'{username:admin,password:newpass}'

Attempts:

3 left

💡 Hint

Common Mistakes

Using single quotes which may not be supported in all shells.

Not quoting keys and values properly in JSON.

The secret-string must be a properly escaped JSON string with double quotes inside double quotes.

4fill in blank

hard

Fill both blanks to create a secret with a description and tags.

AWS

aws secretsmanager create-secret --name MySecret --secret-string [1] --description [2]

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

A"{\"username\":\"admin\",\"password\":\"pass123\"}"

B"My secret for database credentials"

C"Database credentials"

D"{username:admin,password:pass123}"

Attempts:

3 left

💡 Hint

Common Mistakes

Not escaping quotes inside the JSON string.

Using JSON format for description instead of plain text.

The secret-string must be a properly escaped JSON string, and the description is a plain string describing the secret.

5fill in blank

hard

Fill all three blanks to tag a secret with environment and project tags.

AWS

aws secretsmanager tag-resource --secret-id MySecret --tags Key=[1],Value=[2] Key=[3],Value=ProjectX

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

A"Environment"

B"Production"

C"Env"

D"Prod"

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect or inconsistent tag keys.

Not quoting tag keys and values properly.

The tag keys and values must be strings. Here, the first tag key is 'Environment' with value 'Production', and the second tag key is 'Env' with value 'ProjectX'.

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