Basic BigQuery Setup

This is GCP BigQuery connector. Read the following instructions carefully. Go ahead and gather the basic details to connect to your GCP BigQuery project:

• Your GCP BigQuery account and Project information

BigQuery Specifications and Recommendations:

• If you have a restrict ingress firewall or networking policy please whitelist/grantlist the specific DataLakeHouse.io IP addresses from our DataLakeHouse.io IP addresses to allow us to work with your account.

Instructions (Basic Connection Setup)

Scroll down to ensure you review all steps, as needed...

Remember DataLakeHouse.io connects to your BigQuery through Service Account access. We pass all credentials securely with our bank-grade protocols.

1. Grant the BigQuery User role to the Service Account provided in the connection form:
   • Log into your GCP account with an administrator account, usually an account with project owner role access
   • From IAM & Admin menu click on the IAM option, to bing up the permissions for the project: 
   • 

     IAM Setup

     
   • Execute the script by clicking the 'Run Button' 
     • An alternative would be to highlight the entire script and then click the Run button.
2. On the Connection Form : Enter your Other Information
   • Enter in the Name/Alias field, the name you'll use within datalakehouse.io to differentiate this connection from others
   • Click on Save & Test to save the connection and test that we can connect.
3. If updating the form Click Save & Test or just Test
   1. Clicking on Save & Test will again save any changes such as the password change, etc.  You will not be able to change the prefix of the schema that will be the target in the destination. Any test of the connection will attempt to connect to your database with the credentials and info provided.
   2. A message of success or failure will be shown:
      • If success you'll be prompted with the schema objects objects of the database and will need to complete the final steps for configuration shown below.
      • If failure happens with the test connection, the connection is still saved but you will need to correct the failure based on the failure reason information provided in the message
4. GCP Network or Firewall Policy Settings
   1. As mentioned above, if you have configured a restrictive Firewall or Network Policy, please add our grantlist of IP Address:
      • Modify Existing Networking Policy, for example:
        • See GCP gcloud CLI to assign the following IP addresses or contact support for assistance: 34.138.108.146, 34.138.31.121, 35.196.9.75
        • Our IP Grantlist / Whitelist

From time to time we will update the instruction set here to inform you about changes to this connection. If you require any other type of authentication/authorization to connect to your account instance please reach out to our support team via our DataLakeHouse Support Portal.

..