---
title: AWS events-driven discovery
description: The Amazon Web Services \(AWS\) Config service can raise events for any changes in the life-cycle state or the configuration of a cloud resource. The ServiceNow event-driven discovery uses the events to auto-update the latest resource information in the Configuration Management Database \(CMDB\).
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/discovery/aws-events-driven-discovery.html
release: australia
product: Discovery
classification: discovery
topic_type: concept
last_updated: "2026-03-12"
reading_time_minutes: 2
breadcrumb: [Discovery for AWS, Discovery for cloud environment, Discovery, ITOM Visibility, IT Operations Management]
---

# AWS events-driven discovery

The Amazon Web Services \(AWS\) Config service can raise events for any changes in the life-cycle state or the configuration of a cloud resource. The ServiceNow® event-driven discovery uses the events to auto-update the latest resource information in the Configuration Management Database \(CMDB\).

\[Omitted image "aws-events-driven-discovery.png"\] Alt text: Overview of the AWS events-driven discovery

Configure the AWS Config service to send Simple Notification Service \(SNS\) notifications to the ServiceNow instance. For more information, see [Configure AWS Config event notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/aws-config-service-cloud-mgt.md). After you configure the service, it starts sending event notifications to the ServiceNow Cloud Events REST API. When an event meets any one of the following criteria, the API writes it to the Cloud Events \[sn\_cmp\_cloud\_event\] table:

-   The **Type** of the event is **SubscriptionConfirmation**.
-   The **Type** of the event is **Notification** and **messageType** is **ConfigurationItemChangeNotification**.
-   Amazon CloudWatch has raised the event for a change in the tag associated with the Configuration Item \(CI\).

The Cloud Event Scheduler then picks the events in the Ready state for batch processing. During event processing, the event-driven discovery uses response mappings or patterns to update the details of the affected resource in the CMDB. The **sn\_cmp.cloud\_event.use\_response\_mapping\_aws** property determines the CMDB update method. To understand the status of an event, review its state in the Cloud Events \[sn\_cmp\_cloud\_event\] table.

Starting with the Australia release, the **sn\_cmp.cloud\_event.use\_response\_mapping\_aws** property is set to True by default. When this property is set to True, and suitable response mappings are available, the event-driven discovery uses the response mappings to create or update the CI in the CMDB. Otherwise, the event-driven discovery triggers the appropriate patterns to discover the affected resource and create or update the CI in the CMDB.

Starting with the Australia release, use the **sn\_cmp.cloud\_event.parallel\_scheduler\_count** property to scale the Cloud Event Scheduler per the event inflow rate. Running multiple cloud event schedulers in parallel helps to improve the event processing rate of the instance. For more information on scaling the Cloud Event Schedulers, see [Scale the AWS cloud event schedulers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/scale-aws-cloud-event-schedulers.md).

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.