---
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


---

# Cloud Services Catalog administration guide

# Cloud Services Catalog administration guide {#ariaid-title1}

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

After you set up the Cloud Services Catalog application, you must set up some additional items so that your users can request and manage any cloud resource.

## Configuring governance {#cloud-services-catalog-administration-guide__section_dq4_pyx_wzb}

You can use governance tools to restrict the provisioning of cloud resources, such as quotas and policies. For example, you can configure the approval workflow that is used after a user requests a cloud resource, whether an
email is sent after a cloud resource is stopped, and which datacenter is automatically selected when a user selects a resource from a cloud provider. For more information about quotas, policies, and other
governance types, see
[Cloud Governance](https://servicenow-prod.fluidtopics.net/X1MpnCPuXC_MfTVAMiNNRQ "Governance refers to the limitations that you can set on available cloud resources.").

## Populating the Cloud Services Catalog {#cloud-services-catalog-administration-guide__section_bgp_syx_wzb}

After you apply the governance quotas and policies, you must create Cloud Services Catalog items. You can create a catalog item in the following ways:

1. Import a template from Amazon Web Services, Microsoft Azure or Google Cloud Platform.
2. Use or modify an [out-of-the-box](https://servicenow-prod.fluidtopics.net/Djg_j3vi5oZZ~ezGFNgrig "Cloud Services Catalog has Out Of Box Catalog items, actions and policies that you can render, as required.") catalog item.
3. Use a [Terraform template](https://servicenow-prod.fluidtopics.net/eg3__mvq0PtiwOXDHCsnkg "Create a catalog item from the Terraform template to request cloud resource provisioning. Activated catalog items appear in the cloud user portal.").
{#cloud-services-catalog-administration-guide__ul_bzv_sy5_vyb}  
For information about domain separation, multi-repo support with Terraform app, cloud accounts, the Cloud admin portal, or the Cloud API, see the following topics:

* [Use multiple repositories structure with Terraform Connector app](https://servicenow-prod.fluidtopics.net/KpQ7ukIXu3d4OYqOMtq5LQ "You can now discover multiple Terraform configurations from one repository, at any folder level with Terraform Enterprise Config Provider.")
* [Domain separation and Cloud Services Catalog](https://servicenow-prod.fluidtopics.net/EBhK7d6bSnmGyjAYHebt~g "Domain separation is supported in Cloud Services Catalog. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data."): Get additional information about domain separation.
* [Cloud accounts](https://servicenow-prod.fluidtopics.net/jY63f3WTbpyhztut72ZSKQ "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."): Learn about the logical representation in Cloud Provisioning and Governance of all or part of your managed cloud infrastructure.
* [Cloud Admin Portal](https://servicenow-prod.fluidtopics.net/ciKeyHCw1r2AMW4xAyrWFA "The Cloud Admin Portal is a role-based portal. You can manage, design, govern, operate, and analyze all your cloud resources from a unified base."): Manage, design, govern, operate, and analyze all your cloud resources from this portal.
* [Cloud API (CAPI)](https://servicenow-prod.fluidtopics.net/Pn~gp0iGHqa2lM2vdcdeSg "The Cloud API (CAPI) enables you to integrate Cloud Provisioning and Governance with cloud providers using REST APIs."): Integrate Cloud Provisioning and Governance with cloud providers by using REST APIs.
{#cloud-services-catalog-administration-guide__ol_ib4_jnf_mxb}
* **[Cloud Services Catalog and Terraform Connector](https://servicenow-prod.fluidtopics.net/~DdlZ6sMMcLegUkcHpqHhw)**   
  Use the Cloud Services Catalog app with Terraform Connector support with all its features that help in provisioning and managing cloud resources across various public and private clouds.
* **[Permissions management for Cloud Services Catalog](https://servicenow-prod.fluidtopics.net/aXQEeuwZMXZIMXDdYPv0jw)**   
  Permissions are your group-level access rights to features and actions in Cloud Services Catalog.
* **[Policies and permission levels on services](https://servicenow-prod.fluidtopics.net/_LUdVD8Fc7S4KHDdREQ5Yg)**   
  Configure policies with the necessary level of permissions to provide access to the AWS, Azure, ADO, Ansible and Google Cloud services, respectively.