Hey! thanks for responding. Yes, i do mean i'm connecting to GCP from a local laptop.

Locally, what works is the first code snippet i attached, the creds_path is just a string containing the path to the service account json, since even with GOOGLE_APPLICATION_CREDENTIALS set, just the gs:// path did not suffice.

However, with the cloud run application, none of this works. Including using all appropriate options mentioned in the docs here:https://lancedb.github.io/lancedb/guides/storage/#google-cloud-storage.

Usually, for google clients, setting the path to service account is not necessary in cloud run, as long as the service account connected to the cloud run container has the necessary permissions (which it does). I still can't connect to the bucket through the .connect() function.

Usually, for google clients, setting the path to service account is not necessary in cloud run, as long as the service account connected to the cloud run container has the necessary permissions (which it does). I still can't connect to the bucket through the .connect() function.

I agree this is the standard and much easier path. That is normally how I setup GCP instances as well. I configure the VM to have a service account with the appropriate credentials and then check the "Allow full access to all Cloud APIs" checkbox. After that I'm usually able to usegs:// URLs without any storage options. I haven't used cloud run before but can maybe give it a try.

Locally, what works is the first code snippet i attached, the creds_path is just a string containing the path to the service account json, since even with GOOGLE_APPLICATION_CREDENTIALS set, just the gs:// path did not suffice.

I think the environment variables for a service account json file areGOOGLE_SERVICE_ACCOUNT,GOOGLE_SERVICE_ACCOUNT_PATH, orSERVICE_ACCOUNT (these are all aliases). I believe thatGOOGLE_APPLICATION_CREDENTIALS is for using a service account key or "Workforce Identity Federation".

The service account has the required permissions, I just created a new one and deployed it to check if it works but it doesn't.

Also, the "Allow full access to all Cloud APIs" is I think the option that shows up when creating a VM but not Cloud run - my project is in a container deployed with cloud run.

As for theGOOGLE_APPLICATION_CREDENTIALS env variable, my bad - i had set that but was just using the other aliases for the storage options route.