# google-github-actions/upload-cloud-storage "bucket not found"

> Fix google-github-actions/upload-cloud-storage "bucket not found" caused by a wrong bucket name or missing access.

Source: https://latchkey.dev/learn/github-actions/google-github-actions-upload-cloud-storage-bucket-not-found  
Updated: 2026-06-26

The action uploads to a named GCS bucket using the authenticated service account. A wrong name, wrong project, or unauthorized account resolves as bucket not found.

## Diagnose it: what token do you actually have?

Permission failures in Actions are almost never about your repository settings alone. Three things combine: the default `GITHUB_TOKEN` permission set for the repo or organization, the `permissions:` block in the workflow, and whether the event is a fork pull request, which downgrades the token to read-only regardless of everything else.

```.github/workflows/ci.yml
- name: Show the token scopes actually granted
  run: |
    curl -sI -H "Authorization: Bearer $GITHUB_TOKEN" \
      https://api.github.com/ | grep -i "^x-oauth-scopes\|^x-accepted"
    echo "event: ${{ github.event_name }}"
    echo "fork PR: ${{ github.event.pull_request.head.repo.fork }}"
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```

> If `fork PR` prints `true`, stop looking at `permissions:`. A fork pull request gets a read-only token by design, and no workflow-level grant can raise it.

## Grant the narrowest permission that works

Declaring a `permissions:` block switches the job from the repository default to exactly what you list, so an incomplete block is a common cause of a new failure right after someone tightened security. List every scope the job needs, not just the one that failed.

```.github/workflows/ci.yml
permissions:
  contents: read        # checkout
  packages: write       # push to GHCR
  id-token: write       # OIDC to a cloud provider
  pull-requests: write  # comment on or label a PR
  checks: write         # publish check runs
```

> Set `permissions` at the job level rather than the workflow level where you can. A workflow-level grant applies to every job, including ones that only run tests.

## FAQ

### What causes google-github-actions/upload-cloud-storage "bucket not found"?

There are 3 common causes: wrong bucket name, service account lacks access, and wrong project context. A typo or environment mismatch points at a bucket that does not exist.

### How do I fix google-github-actions/upload-cloud-storage "bucket not found"?

Authenticate, then target the correct bucket. Run google-github-actions/auth before the upload.

### What does google-github-actions/upload-cloud-storage "bucket not found" actually mean?

The upload step fails with "bucket doesn't exist" or a 404/403 on the bucket.

### How do I stop google-github-actions/upload-cloud-storage "bucket not found" happening again?

Parameterize bucket names per environment to avoid pointing dev at a prod bucket. The prevention section lists 2 changes that keep it from recurring.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt