Check ID:
Provider: AWS
Service:
Severity: LOW
Categories:
Resource type:
rds_instance_event_subscription_parameter_groupsProvider: AWS
Service:
rdsSeverity: LOW
Categories:
loggingResource type:
AwsRdsEventSubscriptionWhat this check verifies
RDS event subscriptions for DB parameter groups notify onconfiguration change events (or all categories) when the subscription is enabled
Risk
Missing alerts on parameter changes erodes visibility. Attackers or mistakes can lower TLS requirements, disable auditing, or relax auth, enabling data exposure (confidentiality), unauthorized writes (integrity), or outages from unsafe settings (availability).Recommendation
Create and maintain an SNS-backed event subscription for DB parameter groups that includesconfiguration change (or all) and keep it enabled.
- Apply least privilege to SNS topics
- Route to on-call/SIEM and test alerts
- Enforce change control and monitoring across all Regions
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws rds create-event-subscription —subscription-name <example_resource_name> —sns-topic-arn <sns-topic-arn> —source-type db-parameter-group —event-categories “configuration change” —enabled
References
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Events.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/rds-controls.html#rds-21
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = rds_instance_event_subscription_parameter_groups. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks