--- title: Cloud accounts description: 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. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/cloud-configuration-governance/cloud-accounts.html release: australia product: Cloud Configuration Governance classification: cloud-configuration-governance topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 4 breadcrumb: [Cloud Provisioning and Governance administration guide, Cloud Provisioning and Governance, ITOM Cloud Accelerate, IT Operations Management] --- # Cloud accounts 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. From a cloud account, you can: - Add LDCs. A logical datacenter \(LDC\) is a region-specific virtual cloud that is associated with a service account. The datacenter hosts your cloud resources. - Run Discovery on LDCs to update the CMDB with configuration changes or life cycle changes \(create/modify/terminate\) for each resource in each logical datacenter \(LDC\) that is associated with the cloud account. - Set capacity limits on cloud services like virtual machines, virtual CPUs, virtual networks, aggregate storage volume size, and others. Set limits to help ensure that cloud resources are provisioned at appropriate scales. Limits are especially important for capacity-constrained environments like private clouds. - Publish a cloud account to enable business teams to deploy stacks. ## Structure of a cloud account An advantage of cloud accounts is that you can group specified service accounts with only the regions \(datacenters\) that you want to allow cloud resources in. For example, your AWS account could have more than a dozen datacenters globally. However, you might use only one or two regions. To conform with your security and compliance rules, you might not want any resources provisioned to additional regions around the world. \[Omitted image "cloud-acct-makeup.png"\] Alt text: Structure of a cloud account A cloud account can contain as many service accounts as necessary in the following scenarios:
| Structure | Supported | Not supported |
|---|---|---|
| Add the same service account as many times as necessary, provided each entry is associated with a different LDC. | X | |
| Add the same LDC from different service accounts in one cloud account. | X | |
| Add different LDCs from different service accounts to a particular cloud account, provided the regions are not the same.Example: You have us-west-1 in serviceaccount1 and us-west-2 in serviceaccount2. Both can be added to cloudaccount1. However, both us-west-1 in serviceaccount1 and us-west-1 in serviceaccount2 cannot be added to cloudaccount1. | X |