Skip to main content
Book a demo

Connect Google BigQuery to Crush

Give Crush governed access to Google BigQuery’s 9 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Crush setup guide

Set up

Add Google BigQuery to Crush in four steps

Admins approve the server once. Everyone in Crush then gets it through the same governed connection.

  1. 1

    Approve Google BigQuery in Runlayer

    Add Google BigQuery from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Crush to Runlayer

    Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Google BigQuery’s 9 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Crush setup guide
  3. 3

    Sign in to Google BigQuery

    Each user signs in to Google BigQuery with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Google BigQuery from Crush

    Google BigQuery’s approved tools appear in Crush. Every call is checked against policy and recorded.

Tools

9 Google BigQuery tools in Crush

Runlayer policy decides which of these Crush users can call.

  • Cancel job

    Cancel a running BigQuery job.

  • Execute SQL

    Run a SQL query in the project and return the result.

  • Execute SQL readonly

    Run a read-only SQL query in the project and return the result.

  • Get dataset info

    Get metadata information about a BigQuery dataset or BigLake namespace.

  • Get job

    Get information and status about a BigQuery job.

  • Get query results

    Get the results of a BigQuery SQL query job.

  • Get table info

    Get metadata information about a BigQuery table or BigLake table.

  • List dataset IDS

    List BigQuery dataset IDs and BigLake namespaces in a Google Cloud project.

See all 9 Google BigQuery tools

Control

What Runlayer can see and stop in Crush

Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.

  • Gateway policy (available)

    Every Google BigQuery call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination