Send Amazon EventBridge events to Observability Platform

1. Create an API token.
2. Create an API destination.
3. Create an Amazon EventBridge rule, depending on which events you want to send to Observability Platform:
   • Create an EventBridge rule for specific events, such as Amazon CloudWatch events.
   • Create an EventBridge rule for AWS Health events to send those events to Observability Platform.

​

Create an API token

​

Create an API destination

1. Create an API destination by completing the steps in the Amazon EventBridge documentation.
2. Configure the API destination you created:
   1. For the Authorization type, select API Key. Enter API-Token as your API key name, and enter the API token you created as the value.
   2. For the destination endpoint, enter https://ADDRESS/api/v1/data/events and select POST as the HTTP method. Replace ADDRESS with your company name prefixed to your Observability Platform instance that ends in .chronosphere.io. For example, MY_COMPANY.chronosphere.io.
   3. For the Invocation rate limit per second, enter 5 as the value.
   4. Select Use an existing connection and select the connection you created.

​

Create an Amazon EventBridge rule

1. Create an Amazon EventBridge rule that reacts to events:
   • Define the rule detail: Enter details for the rule and select Rule with an event pattern as the rule type.
   • Build the event pattern: Select Use pattern form as the creation method, and define the event pattern.
   • Define the target: Select EventBridge API destination as the target type, choose your existing API destination from the list, and select Create a new role for this specific resource.
2. Expand Additional settings and configure an input transformation to handle mapping from an AWS event to an Observability Platform CreateEvent payload. This definition sends the transformed event to a target instead of the original event. You configure an input path to define variables, and then configure an input template to match your event payload.
3. Configure the input path to reference parameters in your event and store those values in variables. For example:
   Copy

   Ask AI

   {
     "time": "$.time",
     "resources": "$.resources",
     "detail": "$.detail",
     "state": "$.detail.state.value",
     "prevState": "$.detail.previousState.value",
     "alarmName": "$.detail.alarmName",
     "description": "$.detail.configuration.description",
     "detail": "$.detail",
     "region": "$.region"
   }
   

4. Configure the input template to specify the information you want to pass to your target. This template matches your event payload and uses the variables defined in your input path. You must surround all variables with angle brackets <>. For example, the following template defines an Amazon CloudWatch input:
   Copy

   Ask AI

   {
     "event": {
       "happenedAt": "<time>",
       "category": "alerts",
       "labels": {
         "description": "<description>",
         "aws_source": "aws.cloudwatch",
         "region": "<region>"
       },
       "source": "EventBridge",
       "title": "CloudWatch Alarm <alarmName> is in state <state>",
       "type": "CloudWatch_Alarm_State_Change",
       "payload_object": <detail>
     }
   }
   

5. For each additional event type you want to map to a change event, configure a rule and select your existing API destination as the target. Each rule can have its own input transformer.

​

Create an Amazon EventBridge rule for AWS Health

1. Create an Amazon EventBridge rule for AWS Health.
2. In the step where you choose the target type on the Select targets page, configure an input transformation to handle mapping from an AWS event to an Observability Platform CreateEvent payload. This definition sends the transformed event to a target instead of the original event.
3. Configure the input path to reference parameters in your event and store those values in variables. For example:
   Copy

   Ask AI

   {
     "time": "$.time",
     "source": "$.source",
     "detail": "$.detail",
     "service": "$.detail.service",
     "statusCode": "$.detail.statusCode",
     "eventDescription": "$.detail.eventDescription[0].latestDescription",
     "affectedAccount": "$.detail.affectedAccount",
     "region": "$.region",
     "type": "$.detail.eventTypeCode"
   }
   

4. Configure the input template to specify the information you want to pass to your target. This template matches your event payload and uses the variables defined in your input path. You must surround all variables with angle brackets <>. For example, the following template defines an AWS Health input:
   Copy

   Ask AI

   {
     "event": {
       "happenedAt": "<time>",
       "category": "alerts",
       "labels": {
         "description": "<description>",
         "aws_source": "aws.health",
         "region": "<region>",
         "service": "<service>",
         "statusCode": "<statusCode>",
         "affectedAccount": "<affectedAccount>",
       },
       "source": "EventBridge",
       "title": "AWS Health <alarmName> is in state <state>",
       "type": "AWS Health Event",
       "payload_object": <detail>
     }
   }
   

5. Complete the remaining steps in the AWS Health documentation to create the EventBridge rule.

​

Troubleshooting

1. Create a queue in Amazon SQS.
2. Open the Amazon EventBridge rule you created previously.
3. Click the Targets tab and then click Edit.
4. Expand the Additional settings section.
5. In the Dead-letter queue section, click Select an Amazon SQS queue in the current AWS account to use as the dead-letter queue, then select the SQS queue you created.
6. Update the Amazon EventBridge rule.