---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Exclude AWS resource types from datacenter discovery

# Exclude AWS resource types from datacenter discovery {#ariaid-title1}

Release version: Brazil  
Updated September 15, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
You can configure which AWS resource types to exclude from AWS datacenter discovery, to avoid triggering discovery patterns in regions with only default resources.

## Before you begin

* Verify that you have at least version 1.35.1 of Discovery and Service Mapping Patterns.
* Discover only datacenters with resources by setting the mid.cloud.discovery.sonar.discover_all_aws_datacenters MID Server property to false. For more information, see [Limit AWS discovery to datacenters with resources](https://www.servicenow.com/docs/6S~EBHTJSEJXS_Luq3UIEg "Optimize AWS discovery by limiting it to datacenters with resources.").

Role required: discovery_admin

## About this task

Some resource types, such as default Virtual Private Cloud (VPC) and security groups, exist in all regions regardless of whether workloads are deployed there. You can use the
sn_itom_pattern.discovery.aws.ldc.excluded_resource_types system property to exclude these resource types. The default value of the property is empty, which includes all supported resource types in
the query. Excluding these resources gives a more accurate view of which datacenters are active.

## Procedure

1. In the navigation filter, enter <kbd class="ph userinput">sys_properties.list</kbd>.
2. In the Name column, search for the <kbd class="ph userinput">sn_itom_pattern.discovery.aws.ldc.excluded_resource_types</kbd> property.
3. Select the sn_itom_pattern.discovery.aws.ldc.excluded_resource_types property.
4. In the Value field, enter a comma-separated list of AWS resource type identifiers to exclude.  
   For example: <kbd class="ph userinput">ec2:vpc,ec2:security-group</kbd>.

   For a list of AWS resource type identifiers, go to the [AWS Documentation](https://docs.aws.amazon.com/) and search for the "Resource types you can search for with Resource Explorer" article.
5. Select Update.
**Related tasks**   

* [Limit AWS discovery to datacenters with resources](https://www.servicenow.com/docs/6S~EBHTJSEJXS_Luq3UIEg "Optimize AWS discovery by limiting it to datacenters with resources.")  
**Related reference**   

* [AWS discovery using patterns](https://www.servicenow.com/docs/Y0yjdHKR~_I76hi21l9C4A "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")