KeyKeeperGoogle Cloud
How an agent gets a Google Cloud key through KeyKeeper, what to choose on console.cloud.google.com, and how KeyKeeper verifies it.
| Template id | google-cloud (also gcp, google-service-account) |
|---|---|
| Field | google-application-credentials → GOOGLE_APPLICATION_CREDENTIALS · credential file |
| Key looks like | shown once when created |
| Created at | console.cloud.google.com |
| Verified by KeyKeeper | not verified |
| Template checked | 2026-09-15 |
What the agent does
keykeeper providers show google-cloud
keykeeper save --provider google-cloud --from-file /path/to/google-application-credentials.json --create --purpose "what this task does"
keykeeper run -c google-cloud -- <your command>--provider google-cloud fills in the credential id and the field. The environment
variable is the one Google Cloud's own tools read, so nothing has to be mapped.
What only you can do
What to choose
Prefer Application Default Credentials or workload identity. If a downloaded key is unavoidable, use a dedicated service account with resource-level, task-specific IAM roles — never Owner or Editor.
The agent is told the same thing. It opens the page for you and says what to pick; it never logs in, passes 2FA or pays on your behalf.
What KeyKeeper checks
- Before writing: the value must look like a Google Cloud key (shown once when created). A wrong paste is refused before anything is stored, and the agent is told why — without the value.
- After saving: Google Cloud offers no read-only endpoint KeyKeeper can use, so the first real call is the test.
Rotation and expiry
User-managed service-account keys usually remain valid until revoked, but organization policy can impose expiry. Record a date only when the console or policy shows one. Rotate or revoke at console.cloud.google.com.