Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
rds_instance_integration_cloudwatch_logsProvider: AWS
Service:
rdsSeverity: MEDIUM
Categories:
loggingResource type:
AwsRdsDbInstanceWhat this check verifies
RDS DB instances are configured to publish database logs to CloudWatch Logs (e.g.,error, general, slowquery, audit).
The evaluation identifies instances that have log exports enabled to a CloudWatch log group.
Risk
Without centralized RDS logs, database activity lacks visibility, hindering detection and response. Credential misuse, SQL injection, data exfiltration, and privilege abuse may go unnoticed, risking confidentiality and integrity. Unseen errors and slow queries can lead to outages, impacting availability.Recommendation
Enable export of relevant RDS logs to CloudWatch Logs (error, general, slowquery, audit) and standardize across engines. Enforce least privilege on log access, set retention, and define metrics/alarms for critical patterns. Integrate with a SIEM. Apply separation of duties and defense in depth to protect log integrity and monitoring.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/RDS/log-exports.html
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/publishing_cloudwatchlogs.html
- https://repost.aws/knowledge-center/rds-aurora-mysql-logs-cloudwatch
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_integration_cloudwatch_logs. 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