Requirements
- Admin privileges for your Sigma organization
- Permission to create a service account on your Google Cloud project
Connecting your Warehouse to Sigma
Creating a BigQuery Service Account
Before you connect to Sigma, you will need to visit your Google Cloud Platform (GCP) console to create a service account and generate a json private key for your BigQuery instance.
What is a service account, and why do I need one?
A GCP service account is a type of Google account that can securely communicate over Google APIs on your behalf. The service account you create in the steps below will act as a middleman between Sigma and your BigQuery warehouse.
To learn more about service accounts, visit Google’s service account documentation.
Account Permissions / Roles
When creating your service account, you will need to grant it specific access permissions. These permissions are called Roles.
To run BigQuery with Sigma, please grant your service account the following roles:
- "BigQuery Data Viewer"
- "BigQuery Job User"
- "BigQuery Data Editor" - This role is only required if you intend to enable write access on your connection.
Create a Service Account
We have included instructions below to create your service account. However, please be aware that this guide may not always be up to date with the most recent GCP console changes, as GCP is not managed by Sigma.
For Google’s instructions, visit Creating and enabling service accounts for instance.
-
Log into your GCP console.
-
Open the Navigation menu.
-
Hover over ‘IAM & Admin’ and select `Service Accounts` from the submenu.
-
Click ‘+ CREATE SERVICE ACCOUNT’ in the service accounts header.
-
Under Service account details, add an account name, ID, and optional description.
Click ‘CREATE’. -
Under Service account permissions, add the following roles:
- "BigQuery Data Viewer"
- "BigQuery Job User"
- "BigQuery Data Editor" - This role is only required if you intend to enable write access on your connection.
-
Click ‘CONTINUE’.
-
[optional] Under Grant users access.... you may choose to grant other users access to your new service account.
This step is not necessary for connecting to Sigma. -
Click ‘+ CREATE KEY’ to create a json private key.
A file will be downloaded to your computer, which you will later use when connecting to Sigma.
Creating a Connection in Sigma
-
If you have not already created a BigQuery Service Account, please do so now.
-
In Sigma, open your Admin Portal by selecting ‘Administration’ in the user menu at the top right of your screen.
-
Select the ‘Connections’ page from the left hand panel.
-
Click the ‘Create Connection’ button.
-
Name your connection.
-
Select ‘BigQuery’ under warehouse type.
You will then be prompted to specify your 'Connection Credentials'.
-
Under Billing project ID, enter your GCP ‘Project ID’. This can be found under ‘Project Info’ on your GCP console dashboard. Find your project id.
-
Under Service account, paste the json key you created when setting up your service account. The key is located in the .json file that was downloaded to your computer when you created your service account.
-
[optional] Under Connection Features, you can set a connection timeout and/or enable write access*.
*The "BigQuery Data Editor" role is required for write access.
Write access is required for CSV Upload, Materialization, and Dataset Warehouse Views. -
After completing the form, click the ‘Create’ button near the top right of your screen.
Confirming your Connection
After you have created your connection, you can confirm that your data is accessible by visiting the Connections section of Sigma’s left hand navigation panel.
-
If you are still in the Admin Portal, click the X in the top right corner of your screen to close the Admin Portal and navigate back to the home page.
The navigation panel can be opened and closed from any other Sigma page by clicking the green hamburger menu in the top left corner of the page. -
In the navigation panel, click ‘Connections’.
-
Select your new connection from the available list.
-
From here, you can navigate through your connection’s schemas and tables, confirming the connection was successful.
