Events in Amazon EventBridge

  • Latest Dynatrace
  • Explanation
  • Published Sep 25, 2025

Overview

Amazon EventBridge (EB) is a centralized fully managed serverless event router. It's common to use it as a destination event bus, mainly in event-driven use cases (infrastructure or application). During the events onboarding, Dynatrace will (by default) create few resources:

  • An EventBridge rule which registers aws.health events pattern, and that will be attached to the default EventBridge bus.
  • A partner API destination which acts as the rule destination.
  • A connection to the Dynatrace API destination, from AWS to the Dynatrace platform.

Event publish workflow

When the rule is triggered, aws.health events will be published to the Dynatrace platform purpose-built event ingest API (API destination). AWS health events (source='aws.health') ingest, store and present logic:

  • All successfully published events which do not include any Amazon Resource Name (ARN) name of the affected resource, are only linked to the AWS Account entity (node).
  • If the health events were originated from Amazon EC2/AWS VPN AWS resources, those events are designed to be linked to the their respective entities (nodes).
  • Successfully linking the events enables signals in context, allowing the query the events and view their affected AWS resources.

Other successfully published (generic, any source) type events are designed to follow this logic:

  • All successfully published generic events which do not include any Amazon Resource Name (ARN) name of the affected resource, are only linked to the AWS Account entity (node).
  • If one of the affected AWS resource Amazon Resource Name (ARN) is included as part of the event, we will parse it and attempt to link it to the respective entities (nodes).
  • Successfully linking the events enables signals in context, allowing the query the events and view their affected AWS resources.

Where to find the events in Dynatrace?

Any published EventBridge event is stored as a Grail event. From any notebook use this simple DQL: fetch events.

Native event

An event for which the Dynatrace platform is able to link to the relevant effected AWS resource (entity—node).

Generic event

An event for which the Dynatrace platform is not able to link to the relevant effected AWS resource's entity (node), and is only able to link it to the account entity (node).

Onboard Amazon EventBridge events

AWS Organizations

For AWS Orgaizations Member account it is an anti-pattern to update the account directly, such an update should be carried-out from the AWS Org Admin delegated account by the Org Administrator.

If you are creating a new connection New Connection UI-Based wizard:

  1. At the CloudFormation deployment step locate the "Event ingest" parameter section.
  2. Set the "Enable events ingest" parameter to TRUE.
  3. Set the "Regions to ingest events from".

If you wish to onboard events for any existing connection:

  1. Go to the AWS CloudFormation console and locate the primary CloudFormation stack (the name follows the connection name, for example MyProd3East).
  2. Initiate a stack update.
  3. Use Existing Stack.
  4. In Parameters > Events ingest, set the Enable events ingest parameter to TRUE, provide a single or combination of AWS Region(s), separated by commas.
  5. Start the update.
Using the AWS CLI

The AWS CLI can also be used to onboard events using a CloudFormation Stack update with the proper parameters.

Related tags
Infrastructure Observability