Cloud class

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 2 minutes de lecture

    • Description, identification rule, and other important schema structures for the CMDB cloud classes.

    For descriptions of common CMDB tables in a base system, see CMDB tables descriptions.

    Figure 1. AWS/Azure/OpenStack class model​
    AWS/Azure/OpenStack class model.
    Figure 2. IBM Datacenter Cloud Schema model
    IBM Datacenter Cloud Schema model.
    Figure 3. Google Datacenter Schema Model
    Google Datacenter Schema Model.

    Cloud schema description

    ServiceNow has extensive models of cloud environments including Amazon Web Services (AWS), Microsoft Azure service, Google Cloud Platform (GCP), and IBM Cloud. Focusing on the compute side, the models for cloud environments and for Virtual Servers are similar. For example, instances of Amazon Elastic Compute Cloud (EC2) and Microsoft® Azure Cloud Compute, are an extension of Virtual Machine instances, where CIs are typically created by connecting directly to cloud inventory. However, Virtual Machine instances do not represent actual usage of the cloud instance.

    Cloud Service Account [cmdb_ci_cloud_service_account] is the main class for tracking cloud accounts such as AWS, GCP, and Azure (replacing for example, use of the cmdb_ci_aws_account table for AWS).

    For example, you can represent a Linux guest host running on Amazon EC2 by the Server [cmdb_ci_server] class, with the IsVirtual attribute set to true and with the relationship Runs on:Runs to the EC2 instance. Integrating the AWS Config Service or the Amazon CloudWatch application, provides information on the EC2 object ID. Running Discovery or another discovery program on the guest Linux host, provides the hostname.

    Ensure the following:
    • Getting the correct UUID which gets stored in the Serial Number [cmdb_serial_number] table.
    • Connecting/creating the cloud instance to Host OS, matching on the UUID/Object ID and creating the Runs On:Runs relationship.

    ​Also, there is a complete model of Storage, Networking, Lamda/Functions in addition to modeling of different regions using the concept of the table Logical Datacenter [cmdb_ci_logical_datacenter] with Hosts:HostedOn relationship with Compute, Storage, and such.

    Identification rule

    The base system contains pre-defined identification rules for cloud schema classes. A cloud object requires the following identification items:​
    • Object ID: Which is synonymous with the IDs that cloud vendors use for each type of cloud resource, such as Azure Compute, EC2, and Amazon Simple Storage Service (S3).

    • Object ID is unique per region and therefore has dependent relationship requiring information from the Logical Datacenter [cmdb_ci_logical_data_center] table, about the region where the cloud resource is being hosted. For example, AWS Datacenter [cmdb_ci_aws_datacenter], Azure Datacenter [cmdb_ci_azure_datacenter], Google Datacenter [cmdb_ci_google_datacenter] that are extended from Logical Datacenter.

      Logical Datacenter itself, has two identifier entries:​
      • Object ID: Unique ID of the logical datacenter where applicable​
      • Region: The region of the cloud resource

    • Logical Datacenter has a dependency on cloud service accounts​, which has two identifier entries:

      • Object ID: Unique ID of the account where applicable.
      • Account ID: The unique Account ID that encompasses the different cloud resources. Account ID is generally more applicable than Object ID.

    For more information, see CMDB Identification and Reconciliation (IRE).