Secret Manager for credentials in GCP - Commands & Configuration

Introduction

Storing passwords and keys directly in your app is risky. Secret Manager lets you keep these sensitive details safe and separate from your code. It helps you control who can see or use your secrets.

When you need to store database passwords securely for your app.

When you want to keep API keys safe and avoid exposing them in code.

When multiple team members need controlled access to sensitive credentials.

When you want to update secrets without changing your app code.

When you want to audit who accessed your secrets and when.

Commands

This command creates a new secret named 'my-db-password' with automatic replication across Google Cloud regions for reliability.

Terminal

gcloud secrets create my-db-password --replication-policy="automatic"

Expected Output

Created secret [my-db-password].

→

--replication-policy - Defines how the secret is replicated across regions.

This command adds a new version to the 'my-db-password' secret with the value 'SuperSecret123'. The echo command sends the secret value to the gcloud command.

Terminal

echo -n "SuperSecret123" | gcloud secrets versions add my-db-password --data-file=-

Expected Output

Added secret version: 1

→

--data-file=- - Reads secret data from standard input.

This command retrieves the latest version of the secret 'my-db-password' so your app or user can use the stored password.

Terminal

gcloud secrets versions access latest --secret=my-db-password

Expected Output

SuperSecret123

→

--secret - Specifies which secret to access.

This command gives user Alice permission to access the 'my-db-password' secret, controlling who can see the secret.

Terminal

gcloud secrets add-iam-policy-binding my-db-password --member="user:[e-mail]" --role="roles/secretmanager.secretAccessor"

Expected Output

Updated IAM policy for secret [my-db-password].

→

--member - Specifies the user or group to grant access.

→

--role - Defines the permission level for the member.

Key Concept

If you remember nothing else from this pattern, remember: keep secrets out of your code and use Secret Manager to store and control access safely.

Common Mistakes

Storing secrets directly in environment variables or code files.

This exposes sensitive data to anyone who can see the code or environment, risking leaks.

Use Secret Manager to store secrets securely and access them at runtime.

Not setting proper permissions on secrets, allowing everyone to access them.

Anyone with access can read or change secrets, causing security breaches.

Grant access only to specific users or services with the least privilege needed.

Hardcoding secret values when adding versions instead of using secure input methods.

Hardcoding can accidentally expose secrets in command history or logs.

Use input redirection or environment variables to add secrets without exposing them.

Summary

Create a secret with 'gcloud secrets create' to store sensitive data safely.

Add secret values as versions using 'gcloud secrets versions add' with secure input.

Retrieve secrets with 'gcloud secrets versions access' when your app needs them.

Control who can access secrets by setting IAM policies with 'gcloud secrets add-iam-policy-binding'.

Practice

1. What is the main purpose of Google Cloud Secret Manager?

easy

A. To host websites and web applications

B. To securely store and manage sensitive information like passwords and API keys

C. To analyze large datasets quickly

D. To create virtual machines for computing tasks

Solution

1. Step 1: Understand Secret Manager's role

   Secret Manager is designed to keep sensitive data safe and accessible only to authorized users.

2. Step 2: Compare options with Secret Manager's function

   Options A, C, and D describe other cloud services, not Secret Manager.

3. Final Answer:

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

4. Quick Check:

   Secret Manager = Secure storage [OK]

Hint: Secret Manager = safe storage for secrets [OK]

Common Mistakes:

• Confusing Secret Manager with compute or storage services
• Thinking it hosts websites or runs code
• Assuming it analyzes data

2. Which command correctly creates a new secret named db-password in Secret Manager?

easy

A. gcloud secrets create db-password --replication-policy="automatic"

B. gcloud secret create db-password --auto-replication

C. gcloud secrets add db-password --replication=auto

D. gcloud create secret db-password --replication-policy=manual

Solution

1. Step 1: Recall correct gcloud syntax for creating secrets

   The correct command uses gcloud secrets create with the secret name and replication policy.

2. Step 2: Check each option's syntax

   gcloud secrets create db-password --replication-policy="automatic" matches the correct syntax exactly. Options A, B, and C have incorrect command structure or flags.

3. Final Answer:

   gcloud secrets create db-password --replication-policy="automatic" -> Option A

4. Quick Check:

   Correct command syntax = gcloud secrets create db-password --replication-policy="automatic" [OK]

Hint: Use 'gcloud secrets create' with replication policy [OK]

Common Mistakes:

• Using 'secret' instead of 'secrets' in command
• Wrong flag names like --auto-replication
• Incorrect command order or missing quotes

3. Given this Python code snippet accessing a secret version:

from google.cloud import secretmanager
client = secretmanager.SecretManagerServiceClient()
name = "projects/my-project/secrets/api-key/versions/latest"
response = client.access_secret_version(name=name)
payload = response.payload.data.decode("UTF-8")
print(payload)

What will this code print if the secret value is supersecret123?

medium

A. supersecret123

B. b'supersecret123'

C. api-key

D. projects/my-project/secrets/api-key/versions/latest

Solution

1. Step 1: Understand the code flow

   The code accesses the latest version of the secret named 'api-key' and decodes the binary data to a UTF-8 string.

2. Step 2: Determine the printed output

   Since payload.data is decoded, the output is the plain string 'supersecret123', not bytes or other values.

3. Final Answer:

   supersecret123 -> Option A

4. Quick Check:

   Decoded secret value = 'supersecret123' [OK]

Hint: Decoded secret data prints as plain string [OK]

Common Mistakes:

• Printing raw bytes without decoding
• Confusing secret name with secret value
• Expecting metadata instead of secret content

4. You try to access a secret but get a permission denied error. What is the most likely cause?

medium

A. The secret value is empty

B. The secret does not exist in the project

C. The secret version is disabled

D. The service account lacks the Secret Manager Secret Accessor role

Solution

1. Step 1: Analyze permission denied error context

   Permission denied usually means the caller lacks rights to access the secret.

2. Step 2: Identify required role for access

   The Secret Manager Secret Accessor role grants permission to read secret versions. Without it, access is denied.

3. Final Answer:

   The service account lacks the Secret Manager Secret Accessor role -> Option D

4. Quick Check:

   Permission denied = missing access role [OK]

Hint: Check service account roles for Secret Accessor permission [OK]

Common Mistakes:

• Assuming secret absence causes permission error
• Ignoring secret version state
• Thinking empty secret causes permission denied

5. You want to rotate a database password stored in Secret Manager without downtime. Which approach is best?

hard

A. Manually update the password in the database and Secret Manager at the same time

B. Delete the old secret and create a new secret with the new password

C. Create a new secret version with the new password and update your app to use the latest version

D. Store the password in a config file instead of Secret Manager

Solution

1. Step 1: Understand secret rotation best practice

   Adding a new secret version allows smooth transition without deleting old data, avoiding downtime.

2. Step 2: Evaluate options for zero downtime

   Create a new secret version with the new password and update your app to use the latest version uses versioning and app update to switch secrets seamlessly. Delete the old secret and create a new secret with the new password deletes data causing downtime. Manually update the password in the database and Secret Manager at the same time risks inconsistency. Store the password in a config file instead of Secret Manager is insecure.

3. Final Answer:

   Create a new secret version with the new password and update your app to use the latest version -> Option C

4. Quick Check:

   Rotate by adding new version, not deleting [OK]

Hint: Rotate secrets by adding versions, not deleting old ones [OK]

Common Mistakes:

• Deleting secrets causing downtime
• Updating database and secret separately risking mismatch
• Storing passwords insecurely outside Secret Manager