---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Setting up Google Cloud Platform on Cloud Services Catalog

# Setting up Google Cloud Platform on Cloud Services Catalog {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Integrate Cloud Services Catalog with your Google Cloud Platform account as a part of the Day 1 configuration task toward setting up CSC for the first time.

## Before you begin

Collect your account settings and credentials from the provider portal. These settings and credentials help you to distinguish the resources in one account from another account and sign in or authenticate to Google Cloud.
Permission policies specify your approvals within the resources in the account.  
Role required:

* Administrator for operation in Google Cloud or Google Cloud Management Console
* sn_cmp.cloud_admin role for operations in CSC
{#setting-up-google-cloud-platform-on-cloud-services-catalog__ul_a2n_wxl_2bc}

To learn more about setting up Google Cloud with CSC
Terraform Connector app for the first time, see [Day 1 setup guide for Google Cloud through Cloud Services Catalog Terraform Connector](https://servicenow-prod.fluidtopics.net/nI9IZ72k2PeusVUKELhf2w "To set up the ServiceNow Google Cloud Connector application for the very first time, you perform the procedures in this \"Day 1\" setup guide. Be sure to perform the procedures in order. After you have performed Day 1 setup, you can perform optional Day 2 setup and configuration procedures as needed and in any order. Detailed instructions for each procedure follow this overview.").

## Procedure

1. Assign roles to Google Cloud users of CSC and to individual users by their activities and responsibilities.  
   For more information, see [Assign roles to Google Cloud Platform users](https://servicenow-prod.fluidtopics.net/bOiEWFXToWRhB4Mvltou6g "You assign Cloud Provisioning and Governance roles to user groups and to individual users based on user activities and responsibilities.").
2. Install and configure MID Servers for Cloud Discovery and Cloud Provisioning and Governance.  
   To ensure secure and reliable communications, the Discovery process communicates with your cloud provider accounts and cloud resources through one or more MID Servers. For more information, see [Install and configure MID Servers to access cloud environments](https://servicenow-prod.fluidtopics.net/J5R6fEzDsXUAwkST18d7jg "Install and configure the MID Servers correctly to enable ITOM products to access to the cloud resources.").
3. Set up the MID Server on your network or in one of your cloud networks and configure it for CSC to use a proxy server.  
   Using a proxy server supports all cloud-based activities, such as running Discovery, billing downloads, provisioning virtual machines, and running life-cycle operations on virtual machines.
4. Configure one or more MID Servers for each datacenter for high performance and security.  
   Data is encrypted to the MID Server and between the MID Server and the API endpoint.
5. Configure the MID Server even if you have already configured other MID Servers while you were setting up Cloud Services Catalog for another cloud provider
6. Create Service Account and the keys (credentials) in Google Cloud if you don not have it.  
   You can securely store the credentials in a service account. You would need Service Account Key Admin (roles/iam.serviceAccountKeyAdmin) IAM role on the project, or the service account whose keys you want to manage. These permissions can be provided by administrator. To securely access data on your provider account, the Discovery process must present the appropriate credentials.

   For more information, see [Set up Google Cloud Platform service accounts](https://servicenow-prod.fluidtopics.net/qT~O6_Q8nNXW9p4Lvvp_wA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Google Cloud Platform (GCP) service accounts.").
7. Set up a cloud account and a service account for Google Cloud Platform.  
   * A service account is a secure record on your instance that stores the credential and access information for your provider account. Discovery uses the information to access your provider account to get the data on each resource in each specified datacenter.
   * A cloud account is the logical representation in Cloud Services Catalog of all or part of your managed cloud infrastructure. A cloud account can include multiple service accounts, including the service accounts from different providers. For each service account, you specify which datacenters to include in the cloud account.
   {#setting-up-google-cloud-platform-on-cloud-services-catalog__ul_x13_bcm_2bc}

   For more information, see [Set up a cloud account and service account for Google Cloud Platform](https://servicenow-prod.fluidtopics.net/e9DGid_zYnAuYByOctP01w "A service account is a secure record on your instance that stores the credential and access information for your provider account. Discovery uses the information to access your provider account to get data on each resource in each specified datacenter. A cloud account is the logical representation in Cloud Provisioning and Governance of all or part of your managed cloud infrastructure. A cloud account can include multiple service accounts — even service accounts from different providers. For each service account, you specify which datacenters to include in the cloud account.").

