AWS Events

Introduction

Amazon Web Services (AWS) generates various events that allow users to monitor and automate responses to changes in their cloud environment. These events can be delivered using services such as Amazon Simple Notification Service (SNS) and Amazon Simple Queue Service (SQS). This document provides details on AWS events supported by SNS and SQS, along with an explanation of key event categories such as EC2 Events, EC2 Auto Scaling Events, and more.

AWS Events Supported by SNS

This below table provides a clear overview of the full set of Amazon SNS event sources categorized by their respective services.

OpsRamp Supported Events from SQS

OpsRamp integrates with AWS SQS to receive and process various events across multiple AWS services. These events help in monitoring cloud resources and generating alerts based on their status. The following AWS services and their respective event types are supported:

Supported AWS Services and Events

Event Details

EC2 Events

Supported Events

• Instance state changes: pending, running, stopping, stopped, terminated, shutting-down.

Alerting Behavior

• If an event indicates the instance state as pending, stopping, stopped, terminated, or shutting-down, the instance is marked as down in the OpsRamp portal, generating a critical alert.
• If the instance state is running, it is marked as UP, and an OK alert is generated.

EC2 Auto Scaling Events

Supported Events

All auto-scaling events.

Alerting Behavior

• If the event status is failed, a critical alert is generated.
• Otherwise, an OK alert is triggered.

ECS Events

Supported Events

• ECS Task state change
• ECS Container Instance state change

Alerting Behavior

• ECS Task state change events are associated with the ECS Cluster.
• ECS Container Instance state change events are linked to the container instance.
• If the last-status of a task is running, an OK alert is generated.
• Otherwise, a critical alert is raised.

EBS Events

Supported Events

• EBS Volume Events: attachVolume and reattachVolume
• EBS Snapshot Events: copySnapshot and shareSnapshot

Alerting Behavior

• If an event result is failed (for example, attachVolume failure or copySnapshot failure), a critical alert is generated.
• Otherwise, an OK alert is triggered.
• If the event is associated with a single resource, the alert is generated for that resource. If it applies to multiple resources, the alert is assigned to the cloud provider.

AWS Backup Events

Supported Events

• Backup Job Events

Alerting Behavior

• AWS Backup sends events when a backup job state changes via Amazon EventBridge.
• If a backup job enters the state FAILED, ABORTED, or EXPIRED, a critical alert is generated for the associated resource in OpsRamp.
• No OK alert is generated, as backup job failures do not transition into a healthy state.

Supported Resource Types

• DynamoDB
• EBS
• EC2
• EFS
• Neptune

See AWS Backup Events Configuration for more details on backup job setup.

AWS Health Events

Supported Events

• Issue
• ScheduledChange

Alerting Behavior

• AWS Health events are always captured as critical alerts.
• For ScheduledChange events, once the end time of the event is reached, the alert is automatically resolved.
• All alerts generated from AWS Health events are associated with the cloud provider.

Redshift Events

Supported Events

All Redshift events.

Alerting Behavior

• Informational (Info) events are categorized as warning alerts.
• Error events generate critical alerts.

RDS Events

Configuration Events

Supported Events

The following events are supported as part of config events:

• Config Configuration History Delivery Status: Logged as an INFO alert.
• Config Configuration Item Change: Logged as an INFO alert.
• Config Rules Compliance Change:
  • NON_COMPLIANT > Critical alert
  • COMPLIANT > OK alert
  • NOT_APPLICABLE > Warning alert