Create an integration to manage access to BigQuery datasets
Google BigQuery is a fast, scalable, secure, fully managed data warehouse service in the cloud, serving as a primary data store for vast datasets and analytic workloads. Google Cloud enables businesses to analyze their data using standard SQL and existing business intelligence tools, promoting insightful decision-making and integration with various Google Cloud services.
Through this integration, Apono helps you securely manage access to your BigQuery datasets.
Apono Connector
Apono Premium
BigQuery Information
Google Cloud Command Line Interface (Google Cloud CLI)
Google Cloud Information
Information for your Google Cloud instance associated with the Apono connector Google-defined:
User-defined
Service Account Name
To integrate BigQuery, you must create a custom role with BigQuery dataset permissions and assign the role to the service account for the Apono connector.
The following instructions in this section use the Google Cloud CLI.
However, you can also create a custom role through the Google Console, and IAM client library, or the REST API. Additionally, you can assign the custom role to the Apono connector through the Google Console.
\
Follow these steps to associate the permissions through the Google Cloud CLI:
In your shell environment, log in to Google Cloud and enable the API.Shell
Set the environment variables.
Create the custom role. Be sure to replace the placeholders (<ROLE_ID>, <TITLE>, and <DESCRIPTION>) with actual values of your choosing for the role ID, title, and description of the role.ProjectOrganization
Using the role ID defined in the previous step, assign the custom role to the Apono connector service account.ProjectOrganization
Follow these steps to complete the integration:
On the Catalog tab, click Google BigQuery. The Connect Integration page appears.
Under Discovery, click Next. The Apono connector section expands.
From the dropdown menu, select a connector.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating a GCP connector.
Click Next. The Integration Config section expands.
Define the Integration Config settings.
Integration Name
Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
Project ID
GCP project where BigQuery is enabled
Dataset Name
Name of the BigQuery dataset to integrate
Click Next. The Custom Access Details section expands.
Define the Get more with Apono settings.
Custom Access Details
Integration Owner
From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
From the Value dropdown menu, select one or multiple users or groups.
NOTE: When Resource Owner is defined, an Integration Owner must be defined.
Resource Owner
Enter a Key name. This value is the name of the tag created in your cloud environment.
From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.
NOTE: When this setting is defined, an Integration Owner must also be defined.
Click Confirm.
Now that you have completed this integration, you can create access flows that grant permission to your BigQuery datasets.
On-prem serving as a bridge between a Google Cloud instance and Apono
providing the most features and dedicated account support
for the BigQuery datatset to be integrated
used to manage Google Cloud resources
(Organization)
(Optional) Instructions explaining how to access this integration's resources
Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters.
To view the message as it appears to end users, click Preview.
NOTE: You can also add the custom_access_details parameter to the apono_integration schema using Terraform. For more information, learn how to in the Terraform Registry.
(Optional) Fallback approver if no is found Follow these steps to define one or several integration owners:
(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several :