--- sourceDocument: Australia ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/australia/servicenow-platform Release : - australia ft:locale : - en-US ft:publication_title : - Australia ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Cloud class # Cloud class {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Cloud class ServiceNow provides comprehensive models for cloud environments, including AWS, Microsoft Azure, Google Cloud Platform, and IBM Cloud. These models focus on the compute aspects, where cloud instances are treated as extensions of Virtual Machine instances. It is essential for managing cloud accounts and resources effectively within the Configuration Management Database (CMDB). Show full answer Show less ## Key Features * **Cloud Service Account:** The main class for tracking cloud accounts such as AWS, GCP, and Azure, replacing older tables like cmdbciawsaccount. * **Instance Representation:** Cloud instances, like EC2 and Azure Cloud Compute, are represented via the Server class with attributes indicating their virtual nature. * **Identification Rules:** Pre-defined rules for cloud schema classes ensure accurate identification of cloud resources through Object IDs that correspond to those used by cloud vendors. * **Logical Datacenter:** This class models cloud regions and their relationships with various resources, enhancing the tracking of cloud assets. ## Key Outcomes By utilizing the cloud class structures, ServiceNow customers can effectively manage cloud resources, ensuring accurate representation and tracking of cloud service accounts and instances. This leads to improved visibility and control over cloud environments, facilitating better resource management and operational efficiency. 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](https://www.servicenow.com/docs/1GLrH0vZKHQqi0lHfIjuTw "List of tables in the CMDB in a base system with its name, label, and a description of the type of information that is stored in the table."). Figure 1. AWS/Azure/OpenStack class model Figure 2. IBM Datacenter Cloud Schema model Figure 3. Google Datacenter Schema Model ## Cloud schema description {#class-cloud__section_sld_v4g_mkb} 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. {#class-cloud__ul_mhp_yqg_mkb} ​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 {#class-cloud__section_egp_xtg_mkb} 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 {#class-cloud__ul_nbh_nrt_4kb} * 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. {#class-cloud__ul_xvk_n5g_mkb} {#class-cloud__ul_nhh_xjz_4kb} For more information, see [CMDB Identification and Reconciliation (IRE)](https://www.servicenow.com/docs/Z8diB6pYFbsGQMgZmJZYfg "The Identification and Reconciliation module provides a centralized framework for identifying and reconciling data from different data sources. It helps maintain the integrity of the CMDB and some non-CMDB tables when multiple data sources are used to create and update CI records.").