> ## Documentation Index > Fetch the complete documentation index at: https://docs.maia.ai/llms.txt > Use this file to discover all available pages before exploring further. # Streaming runner installation on Google Cloud \ \ \ \
Runner typeStreaming
Runner platform
The Streaming runner is a component within Maia that serves as a bridge between the source database and the target cloud data lake or cloud storage, enabling the execution and scheduling of [streaming pipelines](https://docs.maia.ai/docs/streaming/streaming-pipelines.md). The Streaming runner will be hosted in your own infrastructure, using a Hybrid SaaS solution.Once the Streaming runner is configured and started, it operates autonomously without requiring much intervention. The Streaming runner continuously monitors all changes occurring in the source database, consumes those changes from the low-level logs, and delivers them to the designated target data lake or storage. This ensures a continuous and reliable change data capture process.This topic explains how to create a Streaming runner in your Google Cloud infrastructure.> [!NOTE] > > Each Streaming runner can run **only one** Streaming pipeline. Each Streaming pipeline requires a new Streaming runner installation.***## Prerequisites- A Maia account. To register, read [Registration](https://docs.maia.ai/docs/administration/registration.md). Once you have signed up, log in to [Maia](https://app.matillion.com/hub). - An account in Google Cloud to host the Streaming runner. - Access to a cloud secrets service, which is a secure storage system for storing authentication and connection secrets. These secrets are used by the Streaming runner to authenticate itself with the source database and establish a secure connection for capturing the data changes.***## Create a Streaming runner1) In the left navigation, click the **Runners & Instances** icon ![](https://docs.maia.ai/images/global-nav/runners-instances.png), then in the menu, click **Runners**. The **Runners** list lists all Streaming runners currently created, showing their Status, Platform, and Type. 2) Click **Add runner**. 3) Click **Streaming**. 4) Complete the following properties: * **Runner name:** A unique name for your new Streaming runner. Maximum 30 characters. Accepts both uppercase and lowercase A-z, 0-9, whitespace (not the first character), hyphens and underscores. * **Description:** Optionally enter a brief description of the Streaming runner. * **Cloud provider:** The cloud platform that the Streaming runner will be deployed to. Select **GCP**. * **Deployment:** The Streaming runner deployment method. Choose from **GCE** (Google Compute Engine) or **GKE** (Google Kubernetes Engine). 5) Click **Create runner**. 6) This creates a Streaming runner definition in Maia, and displays the following parameters on the **Runner details** page. You will need these parameters to set up the Streaming runner in your Google Cloud infrastructure. * ACCOUNT\_ID * AGENT\_ID * MATILLION\_REGION * OAUTH\_CLIENT\_ID * OAUTH\_CLIENT\_SECRET The screen will also show any optional environment variables needed by the Streaming runner. Click **Reveal** to make the `OAUTH_CLIENT_ID` and `OAUTH_CLIENT_SECRET` values visible before copying. 7) The Streaming runner's [status](#check-streaming-runner-status) is set to **Pending**, which means it is not yet ready to run pipelines. The next step is to deploy the Streaming runner application into your Google Cloud infrastructure, as described below.***## Set up the Streaming runner in your Google Cloud infrastructureSetting up Streaming runners requires access to Google Cloud services, as well as a degree of familiarity with that platform. We recommend going through this process with your Google Cloud administrator.> [!NOTE] > > Google Cloud resources may come with their own pricing independent of any billing you receive from Matillion.Recommendations:- Create new resources specifically for streaming use rather than attempt to use existing cloud resources. - Set up a resource group for your new resources for better organization and billing ease. - Consult your cloud/network administrator for advice on Google Cloud permissions, roles, access and other considerations such as Google Cloud regions. - Keep resources in the same Google Cloud region. Note that all resources and services may not be available in all regions; it is recommended you research your desired region in advance.***## Check streaming runner statusAfter deploying the Streaming runner in your Google Cloud infrastructure, you should return to Maia to verify that it's correctly connected and running.1) In the left navigation, click the **Runners & Instances** icon ![](https://docs.maia.ai/images/global-nav/runners-instances.png), then in the menu, click **Runners**. The **Runners** list lists all Streaming runners currently created. 2) Locate the Streaming runner in the list and check the status: * **Pending:** The Streaming runner has been created but has not yet connected to Maia. * **Running:** The Streaming runner is connected and available for running Streaming pipelines, or is connected and already running a Streaming pipeline. * **Stopped:** The Streaming runner has been stopped. * **Unknown:** The Streaming runner is in an unknown state. This typically means the Streaming runner has lost connection to Maia without being stopped, for example due to networking issues. 3) When the Streaming runner status shows **Running**, it's ready to use. It can be selected in the **Runner** drop-down when you [create a new Streaming pipeline](https://docs.maia.ai/docs/streaming/streaming-pipelines.md#create-a-streaming-pipeline), as long as a pipeline is not already assigned. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.