Fix BigQuery storage.buckets.get Access Error - Skyvia

BigQuery: Does not have storage.buckets.get access to bucket default

Overview

This error occurs because the default Cloud Storage bucket is used in your BigQuery connection. The default bucket is not suitable for operations conducted via the BigQuery API.

Resolution

Create a dedicated Cloud Storage bucket and configure your BigQuery connection in Skyvia to use it instead of the default bucket.

For instructions on creating a bucket, refer to the Google Cloud Storage: Creating buckets documentation. This link BigQuery Connection Setup may also be useful.

    • Related Articles

    • Backup Plan Storage Limits

      Overview Each Skyvia Backup plan includes a fixed storage quota. Once this limit is reached, no further backups - whether scheduled or manual - will be executed until storage is freed or the plan is upgraded. Autoclean Availability by Plan Plan ...
    • Backup Storage Location

      Overview All your backup data is safely stored in Azure GRS in the West US region. Skyvia uses AES-256 encryption — an industry-standard cipher — to keep your information secure. Storage Details Currently, you cannot change the storage location. ...
    • HubSpot: hapikey Permission Error

      Overview This error is common when working with HubSpot and indicates that the API key (hapikey) used for authentication does not have sufficient permissions to access one or more HubSpot objects. Root Causes The error typically occurs for one of the ...
    • Snowflake: invalid_grant Access Token Error

      Overview This error comes from your Snowflake connection because it has become invalid. By default, the Snowflake OAuth refresh token is valid for 90 days. Once it expires, the connection can no longer authenticate and returns the invalid_grant ...
    • UPDATED: Salesforce: Expired access/refresh token

      Overview If you see an "expired access/refresh token" error, your Salesforce OAuth connection is invalid. This happens when the token has expired, been revoked, or invalidated by a Salesforce security policy change. Possible Causes The OAuth token ...