Check ID:
Provider: AWS
Service:
Severity: LOW
Resource type:
rds_instance_copy_tags_to_snapshotsProvider: AWS
Service:
rdsSeverity: LOW
Resource type:
AwsRdsDbInstanceWhat this check verifies
RDS DB instances are assessed for propagating instance tags to their DB snapshots usingCopyTagsToSnapshot.
Aurora engines manage this at the cluster level and aren’t evaluated per instance.
Risk
Snapshots without inherited tags lose ownership, environment, and sensitivity context, degrading visibility and governance. Missing metadata weakens ABAC, cost allocation, and lifecycle policies, enabling unintended backup access, orphaned snapshots, and retention drift that impact confidentiality and availability.Recommendation
EnableCopyTagsToSnapshot on non-Aurora RDS instances so snapshots inherit required metadata. Establish a consistent tag taxonomy and automate enforcement to support least privilege via ABAC, cost tracking, and retention controls. For Aurora, configure tag copy at the cluster level.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws rds modify-db-instance —db-instance-identifier <example_resource_id> —copy-tags-to-snapshot —apply-immediately
References
- https://docs.aws.amazon.com/systems-manager-automation-runbooks/latest/userguide/automation-aws-enable-tags-snapshot-rds-instance.html
- https://docs.aws.amazon.com/securityhub/latest/userguide/rds-controls.html#rds-17
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/RDS/copy-tags-to-snapshot.html
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_copy_tags_to_snapshots. 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