--- 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 --- # Enable Cloud Hardware table # Enable the Cloud Hardware Type class extension {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Enable the Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table to store the predefined virtual machine (VM) hardware type records for Amazon AWS Cloud Microsoft Azure Cloud and Google Cloud Platform (GCP). This class extension helps prevent duplication of the VM hardware type records in the Hardware Type \[cmdb_ci_compute_template\] table, which improves performance for Discovery and related flows. ## Before you begin * Veirfy that the latest versions of the following applications are installed: * CMDB CI Class Models * Discovery and Service Mapping Patterns If the version of Discovery and Service Mapping Patterns is earlier than 1.6.0, see the Knowledge Base article [KB0955939](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0955939). {#enable-hardware-type-class-extension__ul_sgv_rqm_lfc} * Ensure that the application scope is the Discovery and Service Mapping Patterns application. {#enable-hardware-type-class-extension__ul_ksd_1cj_5rb} Role required: admin ## About this task Each cloud service provider offers several predefined VM hardware types, such as t1.micro (AWS), and so on. You can also create your own. By default, Discovery stores the discovered VM hardware types in the Hardware Type \[cmdb_ci_compute_template\] table. This table is a "child" of the cmdb_ci_logical_datacenter class, so the attributes in the Hardware Type table includes the attributes in the cmdb_ci_logical_datacenter class. This model might create duplicate records for each discovered VM hardware type: The count of records for each discovered VM hardware type is determined by the number of service accounts multipled by the Number of logical datacenters. For example, let's assume an organization has an AWS account of t1.micro VM. The organization has 3000 service accounts and 10 Logical Data Centers (LDCs), such as West US. Your next discovery can detect the VM hardware type and create 30,000 records in the Hardware Type \[cmdb_ci_compute_template\] table. This approach could slow down your discovery and related flows. Avoid these issues by storing the predefined AWS and GCP VM hardware types in the Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table. This table extends the Hardware Type \[cmdb_ci_compute_template\] table. Because it's not tied to any LDC or service account, Discovery avoids adding many VM hardware type records to the Hardware Type \[cmdb_ci_compute_template\] table. The Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table uses the object_id and the provider fields in the identification rule. Note: In AWS environments, the discovery pattern discovers hardware types only to the master account's datacenter. It then creates relationships of the discovered hardware types to the corresponding regions in member accounts. * If a discovery schedule is run for both a master account and member accounts, the pattern discovers only the master account's datacenter hardware type. * If a discovery schedule is run for a standalone member account, the pattern discovers that member account's datacenter and its hardware type. * If a discovery schedule is run for a master account after a standalone member account has already been discovered, the pattern doesn't rediscover the hardware type for the member account. Instead, it discovers the hardware type for the master account and maps the relationships between the master and member accounts. {#enable-hardware-type-class-extension__ul_wmz_23h_tfc} ## Procedure 1. In the navigation filter, enter sys_properties.list. 2. In the Name field, search for sn_itom_pattern.use a single hardware type for cloud data centers. 3. Select the sn_itom_pattern.use a single hardware type for cloud data centers property. 4. In the Value field, enter true. 5. Select Update. {#enable-hardware-type-class-extension__steps_vt5_zz3_5rb} ## What to do next 1. Clean up the Hardware Type records. For more information, see the Knowledge Base article [KB1285337](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1285337). Important: The cleanup removes all the existing compute profiles from the CMDB. Therefore, if you have manually added a hardware template to the Hardware Type \[cmdb_ci_compute_template\] table, you must manually add it to the Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table. 2. Rerun the Cloud Discovery. {#enable-hardware-type-class-extension__ol_j3h_z2l_vrb} **Previous topic:** [Activate a disabled pattern](https://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "If you want to use a pattern for discovery that's disabled by default, activate it manually.") **Next topic:** [Improved query performance with direct field population in CI tables](https://servicenow-prod.fluidtopics.net/H_wfVmrRA2K_BT9VRkb6iQ "The Populate Service Account and LDC IN CMDB scheduled job populates the Service Account and Logical Datacenter fields in cloud configuration item (CI) tables, and the Virtual Machine Object field in the Hardware [cmdb_ci_hardware] table. This direct population reduces query complexity and improves query performance.") **Related reference** * [Amazon AWS Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/nnBwzYmMo_kpTZpG3y5~xQ "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.") * [Google Cloud Platform (GCP) Cloud components discovery using Patterns](https://servicenow-prod.fluidtopics.net/M4N6KVOmfeA1DCboNawaBg "Discovery and Service Mapping Patterns uses patterns to discover components of the Google Cloud Platform (GCP) deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.") * [Microsoft Azure Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")