No RDS event subscription configured for this account
- Severity
- Medium
- Service
- RDS
- Check ID
- RDS_NO_EVENT_SUBSCRIPTION
What this check finds
No RDS event notification subscription exists. Without subscriptions, critical database events (failovers, maintenance, configuration changes) are not sent to operations teams.
Passing looks like: RDS event subscription configured.
How to fix it
Create an RDS event subscription for critical event categories.
AWS CLI
aws rds create-event-subscription --subscription-name ops-alerts --sns-topic-arn TOPIC_ARN --source-type db-instance --event-categories maintenance,failure,availability --enabled
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
RDS → Event subscriptions → Create.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More RDS checks
- HighAurora/RDS cluster storage is not encrypted at rest
- HighRDS automated backups are disabled
- HighRDS instance does not have automatic minor version upgrades enabled
- HighRDS instance has zero database connections for 7 days
- HighRDS instance storage is not encrypted at rest
- HighRDS security group allows broad CIDR ingress (broader than /16)
- HighRDS snapshot is public
- MediumAurora/RDS cluster has automated backups disabled