Check ID:
Provider: AWS
Service:
Severity: LOW
Resource type:
rds_cluster_copy_tags_to_snapshotsProvider: AWS
Service:
rdsSeverity: LOW
Resource type:
AwsRdsDbClusterWhat this check verifies
RDS DB clusters are evaluated for theCopyTagsToSnapshot setting that propagates cluster tags to their DB snapshots.
Aurora tagging is configured at the cluster level; instance-level copying isn’t supported.
Risk
Missing tag propagation leaves snapshots without consistent metadata, weakening ABAC, ownership tracking, and retention controls. This can allow overly broad access to backups, hinder incident scoping, and inflate costs-impacting confidentiality and operational governance.Recommendation
EnableCopyTagsToSnapshot on all applicable RDS/Aurora clusters.
- Standardize required tags (owner, environment, data class)
- Use least privilege and ABAC based on tags
- Automate tagging and periodic audits so snapshots inherit metadata and lifecycle policies
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws rds modify-db-cluster —db-cluster-identifier <example_resource_id> —copy-tags-to-snapshot
References
- https://docs.aws.amazon.com/securityhub/latest/userguide/rds-controls.html#rds-16
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Tagging.html#USER_Tagging.CopyTags
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_cluster_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