Events in Amazon EventBridge

Latest Dynatrace
Explanation
Published Sep 25, 2025
Preview

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.

When the rule is triggered, aws.health events will be published to the Dynatrace platform purpose-built event ingest API (API destination).

Once the aws.health events are successfully published to the Dynatrace API, they are transformed and enriched with common attributes.

The aws.health events are then linked to the relevant effected EC2 resource (entity—node), which allows a rapid view in Clouds Clouds, in the context of the effected EC2.

Any published EventBridge event is stored as a Grail event.

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 (entity—node).

Onboard Amazon EventBridge events

Onboarding the events telemetry signal is (currently) only possible after creating a successful AWS connection.

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

Limitations

For now, only aws.health event type is considered a native event and can be linked to EC2 entities.