Reputation: 2012

gsutil copy returning "AccessDeniedException: 403 Insufficient Permission" from GCE

I am logged in to a GCE instance via SSH. From there I would like to access the Storage with the help of a Service Account:

GCE> gcloud auth list
Credentialed accounts:
 - [email protected] (active)

I first made sure that this Service account is flagged "Can edit" in the permissions of the project I am working in. I also made sure to give him the Write ACL on the bucket I would like him to copy a file:

local> gsutil acl ch -u [email protected]:W gs://mybucket

But then the following command fails:

GCE> gsutil cp test.txt gs://mybucket/logs

(I also made sure that "logs" is created under "mybucket").

The error message I get is:

Copying file://test.txt [Content-Type=text/plain]...
AccessDeniedException: 403 Insufficient Permission               0 B

What am I missing?

Upvotes: 128

Answers (10)

Aditya

Reputation: 21

SSH into the VM.
Authenticate your mail using the below command. It will give you a link; paste that into the browser to get the passcode. Copy the passcode and paste it in the SSH terminal.
```
gcloud auth login
```
Use the below command to create the bucket.
```
gsutil mb gs://YOUR_BUCKET_NAME
```

Upvotes: 0

jterrace

Reputation: 67063

One other thing to look for is to make sure you set up the appropriate scopes when creating the GCE VM. Even if a VM has a service account attached, it must be assigned devstorage scopes in order to access GCS.

For example, if you had created your VM with devstorage.read_only scope, trying to write to a bucket would fail, even if your service account has permission to write to the bucket. You would need devstorage.full_control or devstorage.read_write.

See the section on Preparing an instance to use service accounts for details.

Note: the default compute service account has very limited scopes (including having read-only to GCS). This is done because the default service account has Project Editor IAM permissions. If you use any user service account this is not typically a problem since user created service accounts get all scope access by default.

After adding necessary scopes to the VM, gsutil may still be using cached credentials which don't have the new scopes. Delete ~/.gsutil before trying the gsutil commands again. (Thanks to @mndrix for pointing this out in the comments.)

Upvotes: 197

Omar Bara

Reputation: 528

Stop VM
goto --> VM instance details.
in "Cloud API access scopes" select "Allow full access to all Cloud APIs" then Click "save".
restart VM and Delete ~/.gsutil .

Upvotes: 42

Pratik Waware

Reputation: 1

Change the permissions of bucket.

Add a user for "All User" and give "Storage Admin" access.

Upvotes: -11

Yev Guyduy

Reputation: 1549

So I tried a bunch of things trying to copy from GCS bucket to my VM. Hope this post helps someone.

Via SSHed connection:

and following this script:

sudo gsutil cp gs://[BUCKET_NAME]/[OBJECT_NAME] [OBJECT_DESTINATION_IN_LOCAL]

Got this error:

AccessDeniedException: 403 Access Not Configured. Please go to the Google Cloud Platform Console (https://cloud.google.com/console#/project) for your project, select APIs and Auth and enable the Google Cloud Storage JSON API.

What fixed this was following "Activating the API" section mentioned in this link - https://cloud.google.com/storage/docs/json_api/

Once I activated the API then I authenticated myself in SSHed window via

gcloud auth login

Following authentication procedure I was finally able to download from Google Storage Bucket to my VM.

I did make sure to:

Make sure that gsutils are installed on my VM instance.
Go to my bucket, go to the permissions tab and add desired service accounts and set Storage Admin permission / role.

3.Make sure my VM had proper Cloud API access scopes:

Upvotes: 3

Dr. Tyrell

Reputation: 2829

gsutil config -b

Then surf to the URL it provides, [ CLICK Allow ]

Then copy the verification code and paste to terminal.

Upvotes: 56

Adelin

Reputation: 18961

From the docs: https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances#changeserviceaccountandscopes

You need to first stop the instance -> go to edit page -> go to "Cloud API access scopes" and choose "storage full access or read/write or whatever you need it for"

Changing the service account and access scopes for an instance If you want to run the VM as a different identity, or you determine that the instance needs a different set of scopes to call the required APIs, you can change the service account and the access scopes of an existing instance. For example, you can change access scopes to grant access to a new API, or change an instance so that it runs as a service account that you created, instead of the Compute Engine Default Service Account.

To change an instance's service account and access scopes, the instance must be temporarily stopped. To stop your instance, read the documentation for Stopping an instance. After changing the service account or access scopes, remember to restart the instance. Use one of the following methods to the change service account or access scopes of the stopped instance.

Upvotes: 2

Văn Quyết

Reputation: 2526

After you have created the bucket, go to the permissions tab and add your email and set Storage Admin permission.

Access VM instance via SSH >> run command: gcloud auth login and follow the steps.

Ref: https://groups.google.com/d/msg/gce-discussion/0L6sLRjX8kg/kP47FklzBgAJ

Upvotes: 4

TheLoneDeranger

Reputation: 1199

I have written an answer to this question since I can not post comments:

This error can also occur if you're running the gsutil command with a sudo prefix in some cases.

Upvotes: 15

Javier Giovannini

Reputation: 2352

You have to log in with an account that has the permissions you need for that project:

gcloud auth login

Upvotes: 68

gsutil copy returning &quot;AccessDeniedException: 403 Insufficient Permission&quot; from GCE

Answers (10)

Related Questions

gsutil copy returning "AccessDeniedException: 403 Insufficient Permission" from GCE