EventBridge rules - AWS Prescriptive Guidance

EventBridge rules

Amazon RDS events are delivered to Amazon EventBridge, and you can use EventBridge rules to react to those events. For example, you can create EventBridge rules that would notify you and take an action if one specific DB instance stops or starts up, as the following screen shows.

EventBridge rules for DB instance stops and starts

The rule that detects The DB instance has been stopped event has the Amazon RDS event ID RDS-EVENT-0087, so you set the Event Pattern property of the rule to:

{
  "source": ["aws.rds"],
  "detail-type": ["RDS DB Instance Event"],
  "detail": {
    "SourceArn": ["arn:aws:rds:eu-west-3:111122223333:db:database-3"],
    "EventID": ["RDS-EVENT-0087"]
  }
}

This rule monitors the DB instance database-3 only, and watches for the RDS-EVENT-0087 event. When EventBridge detects the event, it sends the event to a resource or endpoint, known as a target. This is where you can specify the action you want to take if the Amazon RDS instance shuts down. You can send the event to many possible targets, including an SNS topic, an Amazon Simple Queue Service (Amazon SQS) queue, an AWS Lambda function, AWS Systems Manager Automation, an AWS Batch job, Amazon API Gateway, a response plan in Incident Manager, a capability of AWS Systems Manager, and many others. For example, you might create an SNS topic that will send a notification email and SMS, and assign that SNS topic as the target of the EventBridge rule. If the Amazon RDS DB instance database-3 has been stopped, Amazon RDS delivers the event RDS-EVENT-0087 to EventBridge, where it gets detected. EventBridge then calls the target, which is the SNS topic. The SNS topic is configured to send an email (as shown in the following illustration) and an SMS.

SNS topic configuration