RDS instance is missing an Environment tag
- Severity
- Low
- Service
- Tagging
- Check ID
- RDS_MISSING_ENV_TAG
What this check finds
The RDS database instance has no 'Environment' tag. Without it, cost allocation reports cannot break down database spend by environment, and lifecycle policies (e.g. automated stop of non-prod databases) cannot target instances reliably.
Passing looks like: RDS instances have an Environment tag.
How to fix it
Add an Environment tag.
AWS CLI
aws rds add-tags-to-resource --resource-name DB_INSTANCE_ARN --tags Key=Environment,Value=prodEnforce via AWS Config required-tags or tag policies.
Names in capitals are placeholders for your own resource. Review a command before you run it.
Compliance
This is an operational hygiene check. It flags something worth tidying rather than a control an auditor asks for, so it is not mapped to a compliance framework.
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