--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # AWS events-driven discovery # AWS events-driven discovery {#ariaid-title1} Release version: Australia Updated October 15, 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 AWS events-driven discovery AWS events-driven discovery enables automatic, real-time updates to your ServiceNow CMDB whenever AWS resource configurations change. Instead of waiting for scheduled Discovery runs, changes detected by AWS Config trigger immediate notifications, ensuring your CMDB stays current with minimal delay. Show full answer Show less The process works as follows: * AWS Config detects a lifecycle or configuration change in an AWS resource. * An SNS notification is sent to the ServiceNow Cloud Events REST API. * The API logs the event in the Cloud Event \[sncmpcloudevent\] table if it matches specific event types (SubscriptionConfirmation, ConfigurationItemChangeNotification, or tag changes detected by CloudWatch). * The Cloud Event Scheduler processes these events in batches and updates the corresponding CIs in the CMDB. * Updates use response mappings when available; otherwise, the system triggers the appropriate Discovery patterns. ## Requirements * Activation of the Discovery (com.snc.discovery) plugin. * Valid AWS service accounts with linked logical datacenters discovered. * Necessary roles: **discoveryadmin** and **sncmp.cloudeventintegration**. * An AWS role with permissions to access SNS, AWS Config, and targeted resource types. * Download and review the Cloud Discovery patterns spreadsheet for user permissions, pattern details, and vendor documentation. Patterns are updated quarterly, so regular checks are recommended. * Follow setup instructions for configuring AWS Config event notifications. ## Configuration Properties Several key properties control AWS events-driven discovery behavior: * **sncmp.cloudevent.useresponsemappingaws**: When true (default), uses response mappings to update or create CIs. Otherwise, triggers Discovery patterns. * **sncmp.cloudevent.parallelschedulercount**: Defines how many Cloud Event Scheduler instances run in parallel to improve event processing speed. Default is 1, adjustable based on event volume. * **sncmp.errorevents.defaultdomain**: Specifies the sysid of the service-provider domain to restrict visibility of failed events to the service-provider administrator. Default is global. ## Domain Separation and Visibility The Cloud Event Scheduler assigns events to domains based on the associated service account. If domain identification fails, events remain unassigned and visible across all domains. Setting the **sncmp.errorevents.defaultdomain** property helps limit failed event visibility to the appropriate administrators, improving security and management. ## Next Steps for Implementation * Configure AWS Config event notifications to enable event-driven updates. * Scale the Cloud Event Scheduler instances as needed to handle your event volume efficiently. * Create database indexes for the Cloud Events table to optimize performance. By enabling AWS events-driven discovery, ServiceNow customers can expect timely and accurate CMDB updates reflecting their AWS environment changes, reducing manual intervention and improving operational visibility. Use AWS events-driven discovery to keep your CMDB current automatically when AWS resource configurations change, without waiting for a scheduled Discovery run. ## How it works {#aws-events-driven-discovery__how-it-works} Figure 1. Overview of the AWS events-driven discovery 1. AWS Config detects a change in the lifecycle state or configuration of a cloud resource. 2. AWS Config sends a Simple Notification Service (SNS) notification to the ServiceNow Cloud Events REST API. 3. The API writes the event to the Cloud Event \[sn_cmp_cloud_event\] table if it meets any of the following criteria: * The Type of the event is SubscriptionConfirmation. * The Type of the event is Notificationand messageType is ConfigurationItemChangeNotification. * Amazon CloudWatch raised the event for a tag change on a Configuration Item (CI). {#aws-events-driven-discovery__ul_pb3_rhz_vvb} 4. The Cloud Event Scheduler picks up events in the Ready state for batch processing and updates the affected resource in the CMDB. When response mappings are available, event-driven discovery uses them to update the CI. Otherwise, it triggers the appropriate Discovery pattern. {#aws-events-driven-discovery__ol_vyd_ljg_skc} ## Requirements for AWS events-driven discovery {#aws-events-driven-discovery__requirements} Before configuring AWS events-driven discovery, verify the following requirements are met: * The Discovery (com.snc.discovery) plugin is activated. * Valid AWS service accounts with associated logical datacenters are discovered. * Required roles: discovery_admin and sn_cmp.cloud_event_integration. * An AWS role with access to SNS, AWS Config, and the resource types you want to track. * Download the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.{#aws-events-driven-discovery__cloud-discovery-api-ph-short-prereq} {#aws-events-driven-discovery__ul_cnr_zjg_skc} For setup instructions, see [Configure AWS Config event notifications](https://www.servicenow.com/docs/d9CxNzq~eM1Xo~ZWc_iSMg "Configure the Amazon Web Services (AWS) Config service to send event notifications to the ServiceNow instance for any changes in the lifecycle state of a resource."). ## Configuration properties {#aws-events-driven-discovery__configuration-properties} {#aws-events-driven-discovery__table_config_properties__entry__2} | Property | Description | |-|-| | sn_cmp.cloud_event.use_response_mapping_aws | Determines the CMDB update method. When set to True and suitable response mappings are available, event-driven discovery uses response mappings to create or update the CI in the CMDB. Otherwise, event-driven discovery triggers the appropriate Discovery pattern. * Type: Boolean * Default: true | | sn_cmp.cloud_event.parallel_scheduler_count | Controls the number of Cloud Event Scheduler instances running in parallel. Increase this value to improve event processing rate when event inflow is high. For more information, see [Scale the AWS cloud event schedulers](https://www.servicenow.com/docs/oUIFspNX_ZxEWuEbQ96mig "Scale the cloud event schedulers to improve the Amazon Web Services (AWS) event processing rate of the ServiceNow instance."). * Type: Integer * Default: 1 | | sn_cmp.error_events.default_domain | The sys_id of the service-provider domain. Set this property to limit the visibility of failed events to the service-provider administrator. * Type: String * Default: global {#aws-events-driven-discovery__ul_efl_1hg_skc} | [ ] {#aws-events-driven-discovery__table_config_properties} ## Domain separation {#aws-events-driven-discovery__domain-separation} During event processing, the Cloud Event Scheduler identifies the domain of the associated service account and assigns it to the event. If domain identification fails before processing, the event can remain unassigned and be visible across all domains. To limit the visibility of failed events to the service-provider administrator, set the sn_cmp.error_events.default_domain property to the sys_id of the service-provider domain. **Related tasks** * [Configure AWS Config event notifications](https://www.servicenow.com/docs/d9CxNzq~eM1Xo~ZWc_iSMg "Configure the Amazon Web Services (AWS) Config service to send event notifications to the ServiceNow instance for any changes in the lifecycle state of a resource.") * [Scale the AWS cloud event schedulers](https://www.servicenow.com/docs/oUIFspNX_ZxEWuEbQ96mig "Scale the cloud event schedulers to improve the Amazon Web Services (AWS) event processing rate of the ServiceNow instance.") * [Create a database index for the Cloud Events table](https://www.servicenow.com/docs/hkIm_i_9zM6MHMfvpJjG9Q "Create a database index from the specified columns of the Cloud Events [sn_cmp_cloud_event] table to improve the AWS cloud event processing performance.") **Related reference** * [AWS discovery using patterns](https://www.servicenow.com/docs/NFaTlkGaSxMWb2bQPsCnCA "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.") * [AWS Events pattern-based discovery](https://www.servicenow.com/docs/azI0rhocpxlyOrU2gCirMQ "Discovery uses event patterns to update Amazon AWS Cloud component data in near real-time. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")