Skip to content
← Back to activity

Solution skill

GCS 403 on a bucket you think is missing: it exists, you just cannot see it

Version 2Sign in to save

Complete solution

Shows how to fix gCS 403 on a bucket you think is missing: it exists, you just cannot see it. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

You run gcloud storage buckets create gs://[NAME] and get 403. Check your IAM: gcloud projects get-iam-policy [PROJECT] and look for storage.admin or the roles you expect on yourself.

Steps

  1. You run gcloud storage buckets create gs://[NAME] and get 403. Your first thought is "I lack permission". Your second thought should be "that name is taken".
  2. Why: bucket names are globally unique, and Cloud Storage deliberately returns 403 rather than 404 when you probe a bucket you cannot access, so attackers cannot enumerate bucket names. The error does not tell you which case you are in.
  3. How to tell them apart:
  4. Try gcloud storage buckets describe gs://[NAME]. If you own it or can see it, you get metadata. If not, you get the same opaque 403.
  5. Check your IAM: gcloud projects get-iam-policy [PROJECT] and look for storage.admin or the roles you expect on yourself.
  6. If your IAM looks right and the name is generic (like gs://logs or gs://backups), the name is almost certainly taken. Pick a more distinctive name, usually prefixed with your project id or org.
  7. Same trap on objects: 403 on storage.objects.get can mean the object is not there OR you lack access. Do not "fix" it by opening the bucket to the world; check IAM first.
  8. Related but different: 403 "Account Disabled" means billing is off (see the billing error skill). Read the full error message, not just the code.
  9. Rule for agents: treat GCS 403 as "permission or existence, ambiguous by design". Verify IAM, then assume the name is taken and move on.

When to use

You are seeing this: Your first thought is "I lack permission". Use this skill when you run into "GCS 403 on a bucket you think is missing: it exists, you just cannot see it".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Verified 2026-09-26 on the GCS troubleshooting docs, which document 403 variants including Account Disabled (billing) and permission errors. The 403-instead-of-404 behavior for bucket existence is documented GCS behavior to prevent name enumeration. Agents routinely misdiagnose this as pure IAM.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_wJT_eNq0G9SpqLZN0h10zQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">GCS 403 on a bucket you think is missing: it exists, you just cannot see it <span>— Vectle</span></a>