Disable or Restrict Cloud Discovery patternsSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Sometimes, there might be a requirement to restrict some of the Cloud Discovery resource types, it depends upon multiple reasons, example excessive data on cloud related tables, this article explains the ways possible and OOB functionality Firstly, yes, we can disable some of the resource discovery from the AWS Discovery, however, it is important that we know which are the resources we will need to disable Why we must need to know the resource types we want to disable?Ans: The Cloud Discovery works in a Orchestration way, we can say dependency way, for example take examples of the Service Account, Datacenter and Virtual machines, the Virtual Machine discovery only happens when the Datacenter discovery successfully completed, and the Datacenter Discovery completes only if the Service Account discovery completes successfully. The rest of the Cloud Discovery patterns also works in the same dependency wayIf we disable any of the Resource discovery without knowing the dependency, it may break rest of the Discovery Once we have the clear information on what resources needed to be disabled, below is the location where the Pattern trigger rules are updated for your reviewhttps://<Instance>.service-now.com/sn_pattern_trigger_rule_list.do?sysparm_clear_stack=trueOOB, there is no other functionality to disable the resource types, however, the only way is to disable the Patterns, below are the Patterns available for AWS, prior disable please complete the above point number 3https://<Instance>.service-now.com/sa_pattern_list.do?sysparm_query=nameSTARTSWITHAmazon&sysparm_first_row=1&sysparm_view=&sysparm_choice_query_raw=&sysparm_list_header_search=trueThe AWS cloud Discovery executed with each Pattern have its own Class, for example, the pattern "Amazon AWS - Availability Zone (LP)" have its own class and create/update the records to "cmdb_ci_availability_zone" table,As you know the AWS have more than 100 resource types, for Discovery it is not possible to create classes for all the resource types, Discovery executes a pattern called "Amazon AWS Resource Inventory" which captures the information of the Resource types which are not having classes and create/update the table "cmdb_ci_cmp_resource" table Q) How "Amazon AWS Resource Inventory" understand which are the ResourceTypes to be captured and update the "cmdb_ci_cmp_resource" table?Ans: The "Amazon AWS Resource Inventory" looks into the table "sa_cloud_inventory_resource_whitelist" for the available configuration for AWS and if there is a valid API configuration those Resources will be updatedhttps://<Instance>.service-now.com/sa_cloud_inventory_resource_whitelist_list.do?sysparm_query=cloud_vendor%3DAWS&sysparm_first_row=1&sysparm_view=Q) Can we add more Resource Types or delete unwanted resource types from the "sa_cloud_inventory_resource_whitelist" table?Ans: Yes of-course, we can add as many resource types we wanted to capture the information, also you may wish to delete some which are not needed, there is no specific limitation as the content in the table is for customer requirement basis, please find the below document on how to add the resource typeshttps://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/service-mapping/reference/aws-resource-inventory.htmlQ) How to identify what kind of resource types can be added?The resource types are actually coming from the AWS, hence the best way to identify the resource Type from the AWS API documentation, the below documentation also have the examples of what is needed from AWS and how to searchhttps://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/service-mapping/reference/aws-resource-inventory.html Hence, depending on what Resource Types need to be disabled from AWS cloud discovery, you may follow the above and disable accordingly