Service account keys management in GCP - Step-by-Step Execution

Process Flow - Service account keys management

Create Service Account

↓

Generate Key for Account

↓

Store Key Securely

↓

Use Key for Authentication

↓

Rotate Key Periodically

↓

Delete Old/Unused Keys

↓

End

This flow shows how to create a service account, generate keys, use them securely, rotate keys regularly, and delete old keys to keep security strong.

Execution Sample

GCP

1. gcloud iam service-accounts create my-sa
2. gcloud iam service-accounts keys create key.json --iam-account=my-sa@PROJECT_ID.iam.gserviceaccount.com
3. Use key.json in app
4. gcloud iam service-accounts keys list --iam-account=my-sa@PROJECT_ID.iam.gserviceaccount.com
5. gcloud iam service-accounts keys delete KEY_ID --iam-account=my-sa@PROJECT_ID.iam.gserviceaccount.com

This sequence creates a service account, generates a key, lists keys, and deletes a key.

Process Table

Step	Action	Command/Operation	Result/State Change
1	Create service account	gcloud iam service-accounts create my-sa	Service account 'my-sa' created
2	Generate key for 'my-sa'	gcloud iam service-accounts keys create key.json --iam-account=my-sa@PROJECT_ID.iam.gserviceaccount.com	Key file 'key.json' created and downloaded
3	Use key in app	App uses 'key.json' to authenticate	App authenticated as 'my-sa'
4	List keys for 'my-sa'	gcloud iam service-accounts keys list --iam-account=my-sa@PROJECT_ID.iam.gserviceaccount.com	Shows list of keys with IDs and creation dates
5	Delete old key	gcloud iam service-accounts keys delete KEY_ID --iam-account=my-sa@PROJECT_ID.iam.gserviceaccount.com	Key with KEY_ID deleted
6	End	-	No further action

💡 All keys managed: created, used, listed, and deleted as needed to maintain security.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	After Step 5	Final
Service Account	None	my-sa created	my-sa with key generated	my-sa with keys listed	my-sa with key deleted	my-sa with updated keys
Key File	None	None	key.json created	key.json known	key.json deleted if old	No unused keys remain

Key Moments - 3 Insights

Why do we need to delete old service account keys?

Old keys increase security risk if leaked. Deleting them reduces attack surface. See execution_table step 5 where key deletion happens.

Can we use a service account without generating a key file?

Yes, if running on Google Cloud resources with default service accounts. But for external apps, keys are needed. Step 3 shows using the key file for authentication.

What happens if we lose the key file?

You cannot authenticate with that key anymore. You must create a new key and delete the lost one to keep security. See steps 2 and 5 for key creation and deletion.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after step 2?

A Key file 'key.json' created and downloaded

B App authenticated as 'my-sa'

C Service account 'my-sa' created

D Key with KEY_ID deleted

💡 Hint

Check the 'Result/State Change' column for step 2 in execution_table.

At which step do we remove an old key?

A Step 1

B Step 3

C Step 5

D Step 4

💡 Hint

Look for the action 'Delete old key' in execution_table.

If we skip step 5, what happens to the keys according to variable_tracker?

A No keys exist

B All keys remain, including old ones

C Only new keys exist

D Service account is deleted

💡 Hint

Check variable_tracker row for 'Key File' after step 5.

Concept Snapshot

Service account keys management:
- Create service account
- Generate keys for authentication
- Use keys securely in apps
- List keys to monitor
- Rotate and delete old keys regularly
- Keep keys safe to protect access

Full Transcript

This lesson shows how to manage service account keys in Google Cloud. First, create a service account. Then generate a key file to authenticate apps outside Google Cloud. Use the key file in your app to access resources. Regularly list keys to see which exist. Delete old or unused keys to keep your project secure. Losing keys means you must create new ones. Managing keys carefully protects your cloud resources.

Practice

1. What is the main purpose of a service account key in Google Cloud?

easy

A. To manage billing information for Google Cloud projects

B. To store user passwords for Google Cloud accounts

C. To allow programs to securely access Google Cloud resources

D. To create virtual machines automatically

Solution

1. Step 1: Understand service account keys

   Service account keys are used by programs, not humans, to access Google Cloud securely.

2. Step 2: Identify the correct purpose

   They provide credentials for applications to authenticate and interact with cloud services.

3. Final Answer:

   To allow programs to securely access Google Cloud resources -> Option C

4. Quick Check:

   Service account keys = secure program access [OK]

Hint: Keys let programs access cloud securely, not users [OK]

Common Mistakes:

• Confusing keys with user passwords
• Thinking keys manage billing
• Believing keys create virtual machines

2. Which gcloud command correctly creates a new service account key for the account [e-mail]?

easy

A. gcloud iam service-accounts keys create key.json --iam-account=[e-mail]

B. gcloud iam service-accounts create key.json --account=[e-mail]

C. gcloud service-accounts keys create key.json --account=[e-mail]

D. gcloud iam keys create key.json --iam-account=[e-mail]

Solution

1. Step 1: Identify correct gcloud command syntax

   The correct command to create a key is gcloud iam service-accounts keys create with the --iam-account flag.

2. Step 2: Match the command with the options

   gcloud iam service-accounts keys create key.json --iam-account=[e-mail] matches the correct syntax exactly.

3. Final Answer:

   gcloud iam service-accounts keys create key.json --iam-account=[e-mail] -> Option A

4. Quick Check:

   Correct command syntax = gcloud iam service-accounts keys create key.json --iam-account=[e-mail] [OK]

Hint: Use 'iam service-accounts keys create' with --iam-account [OK]

Common Mistakes:

• Using 'create' without 'keys'
• Wrong flag like --account instead of --iam-account
• Omitting 'iam' in the command

3. What will be the output of the following command?

gcloud iam service-accounts keys list --iam-account=[e-mail]

Assuming there are two active keys for this service account.

medium

A. A prompt to create a new key

B. An error saying no keys found

C. A list of all service accounts in the project

D. A list showing details of the two active keys including key IDs and creation dates

Solution

1. Step 1: Understand the command purpose

   The command lists keys for the specified service account.

2. Step 2: Interpret expected output

   Since two active keys exist, the output will show their details like key IDs and creation dates.

3. Final Answer:

   A list showing details of the two active keys including key IDs and creation dates -> Option D

4. Quick Check:

   Listing keys shows active keys details [OK]

Hint: List keys command shows active keys info [OK]

Common Mistakes:

• Expecting an error if keys exist
• Confusing keys list with service accounts list
• Thinking it prompts for key creation

4. You run the command:

gcloud iam service-accounts keys delete 123abc --iam-account=[e-mail]

But get an error saying the key ID does not exist. What is the most likely cause?

medium

A. The key ID is incorrect or does not belong to the specified service account

B. The service account email is misspelled

C. You need to create a new key before deleting

D. The project ID is missing from the command

Solution

1. Step 1: Analyze the error message

   The error says the key ID does not exist, meaning the key ID is invalid or not linked to the service account.

2. Step 2: Check command components

   The service account email may be correct, and project ID is not required here if default is set. Creating a key before deleting is unnecessary.

3. Final Answer:

   The key ID is incorrect or does not belong to the specified service account -> Option A

4. Quick Check:

   Invalid key ID causes deletion error [OK]

Hint: Check key ID matches service account keys [OK]

Common Mistakes:

• Assuming project ID is mandatory in this command
• Thinking you must create a key before deleting
• Ignoring key ID correctness

5. You want to rotate service account keys to improve security. Which sequence of actions is the best practice?

hard

A. Delete the old key first, then create a new key and update applications

B. Create a new key, update your applications to use it, then delete the old key

C. Create multiple keys and use them all simultaneously without deleting any

D. Keep using the old key until it expires, then create a new key

Solution

1. Step 1: Understand key rotation best practice

   To avoid downtime, first create a new key and update applications to use it.

2. Step 2: Remove old key after update

   Once applications use the new key, delete the old key to reduce risk.

3. Final Answer:

   Create a new key, update your applications to use it, then delete the old key -> Option B

4. Quick Check:

   New key first, then delete old key [OK]

Hint: Add new key before deleting old one to avoid downtime [OK]

Common Mistakes:

• Deleting old key before updating apps
• Using multiple keys unnecessarily
• Waiting for old key to expire before rotating