Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Cloud account

A cloud account is a logical representation of your managed cloud infrastructure. You can associate a cloud account with one or more logical datacenters (LDCs) at one or more provider accounts — even including LDCs from disparate providers.

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

A cloud account can contain as many service accounts as necessary in the following scenarios:
Table 1. Possible cloud account structures
Structure Supported Unsupported
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

An advantage of cloud accounts is that you can group specified service accounts with only the regions 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.

Update a cloud account

You keep a cloud account in the Draft state until you are ready to make the datacenters and capacity limits available for use — in blueprints and the Cloud User Portal, for example. You can change the state to Published after you run Discovery.

Set up a cloud account

Set up cloud accounts for AWS

Set up cloud accounts for Azure

Set up cloud accounts for VMware

Add a logical datacenter to a cloud account

As needed, you can add logical datacenters to appropriate service accounts.

Add LDCs to an AWS service account

Add LDCs to an Azure service account

Add LDCs to a VMware service account

Set capacity limits on cloud resources

Capacity limits place restrictions on the attributes of cloud resources, such as the number of virtual machines or virtual CPUs, or the total size of all storage volumes. You can set limits on resources separately for each logical datacenter (LDC) in a cloud account.

Set capacity limits on AWS cloud resources

Set capacity limits on Azure cloud resources

Set capacity limits on VMware cloud resources

Changes to site functionality will be made starting around 6am on January 21st (Pacific Time) and lasting approximately 6 hours.  The site may be intermittently unavailable.