--- title: "Add a GCP node" description: "Add a Google Cloud Platform resource for agentless scanning." product: "Guardian" edition: "Classic" type: "workflow" url: "https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/google-cloud-platform-gcp-node/" --- # Add a GCP node Add a Google Cloud Platform resource for agentless scanning. Guardian supports multiple types of Google Cloud Platform (**GCP**) nodes. For example, you can add GCP Compute Engine VM Configuration nodes, GCP Storage Bucket nodes, GCP Kubernetes Engine nodes, and more. Applies to: `Guardian Classic` !!! note Additionally, you can import GCP nodes in bulk rather than individually, as the below process describes. For more information, see [Add Nodes in Bulk via GCP](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-nodes-in-bulk/gcp-nodes/index.md). ## Dependencies To add a GCP node, the following dependencies must be met: - **Linux Connection Manager** – Set up in Guardian. For more information, see [Linux Connection Manager](https://docs.cloudhouse.com/guardian/classic/inventory/connection-managers/connection-managers/linux/linux-connection-manager/index.md). - **Google Service Account** – Set up with the JSON Web Token (**JWT**) generated. For more information, see [Google Cloud Platform Service Account](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/account-setup/google-cloud-platform-service-account/index.md). - **Service Permissions** – Permissions set for the service intended to be scanned. For more information, see [Supported GCP Services](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/supported-cloud-services/supported-gcp-services/index.md). ## Add a GCP node Adding a GCP node to your Guardian instance lets you monitor and track the configuration of a GCP resource. To add a GCP node for Agentless scanning, complete the following steps: 1. In the Guardian web application, navigate to the **Add Nodes** tab (**Inventory** > **Add Nodes**). The **Add Nodes** page is displayed. ![Add nodes tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/add-nodes-tab.png) 2. Type 'GCP' in the search bar. 3. Select the 'GCP' node type you want to add and click the **Go Agentless** button to proceed. The **Connect Agentlessly to [Node Type]** page is displayed. ![Go agentless gcp](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/go-agentless-gcp.png) 4. Here, complete the following options: ![Connect agentlessly gcp](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/connect-agentlessly-gcp.png) **Connection Manager group** drop-down list : The Connection Manager group that is responsible for scanning your GCP node. Select a Connection Manager group from the drop-down list. **[Node Type] Name** field : The name of the node. The value you enter here will be used as the display name in Guardian. !!! note The name of this field changes depending on the GCP node type you select. For example, for 'GCP Kubernetes Engine' node, this field would be labeled 'GCP Kubernetes Engine'. **GCP zone** field : The zone in which the service is hosted. For more information on how to source this, see [Google Cloud Platform Service Account](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/account-setup/google-cloud-platform-service-account/index.md). **GCE service account JWT** field : The JSON Web Token that is required to authenticate the Google Service Account. For more information on how to source this, see [Google Cloud Platform Service Account](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/account-setup/google-cloud-platform-service-account/index.md). 5. Once you've completed the above options click **Scan Node** to add the GCP node to your Guardian instance. Now, Guardian performs an initial scan of the node. You can wait on this page for the scan to finish, at which point you will see a **View Scan** button. To view the results of this initial scan, click **View Scan**. However, you can also navigate elsewhere while Guardian performs its initial scan of the node. You can then view the status of the scan on the [**Job History**](https://docs.cloudhouse.com/guardian/classic/control/job-history/job-history/index.md) page (**Inventory** > **Job History**). For more information on what to do next after adding a node, see below. ## Where next - [*Read* **Node Scan Results** What every scan of a node collected.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/nodes/node-scan-results/index.md) - [*Organise* **Node groups** Group nodes by type, location and more.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/node-groups/node-groups/index.md) - [*Tune* **Scan options** Choose what each scan collects.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/scan-options/scan-options/index.md) - [*Compare* **Configuration differencing** Compare nodes, groups and scans.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/configuration-differencing/index.md) - [*Govern* **Policies** Define the configuration you expect.](https://docs.cloudhouse.com/guardian/classic/control/policies/policies/index.md) - [*Connect* **Integrations** Sync nodes and act on events.](https://docs.cloudhouse.com/guardian/classic/control/integrations/integrations/index.md)