Resource Management
Synchronization, triage, tag-based exclusion and locking of your RDS instances.
Synchronization
SnoozeDB scans all AWS regions in your account to detect RDS instances. The first scan is automatic when the account is connected.
You can trigger a manual scan from the dashboard at any time. New instances are added, instances deleted on AWS are removed.
Triage
Each detected instance goes through a triage system that determines whether it is managed by SnoozeDB or not.
| Status | Meaning | Scheduled |
|---|---|---|
| Active | The instance is managed by SnoozeDB and follows a start/stop schedule | Yes |
| Uncategorized | New instance not yet triaged: waiting for your decision | No |
| Excluded | Instance explicitly excluded from automatic management | No |
Tag-based exclusion
You can exclude instances from automatic management via two mechanisms: AWS tags and organization rules.
Tags are evaluated at each synchronization. A tagged-for-exclusion instance will never be stopped by SnoozeDB, even if it is in the "Active" triage.
AWS Tags
Add the tag snoozedb:exclude=true directly on the RDS instance in the AWS console or via CLI:
aws rds add-tags-to-resource \ --resource-name arn:aws:rds:eu-west-1:123456789012:db:my-database \ --tags Key=snoozedb:exclude,Value=true
Organization rules
From the organization settings, you can define tag-based exclusion rules. For example, exclude all instances with the tag Environment=production. These rules apply to all instances in the organization.
Resource locking
Locking temporarily prevents any automatic action on an instance. Useful during maintenance, migrations or investigations. A lock reason can be added for traceability.
Quotas
The number of instances you can activate ("Active" status) depends on your plan. The Dev plan allows 1 instance, the Scale plan up to 50.
If you have reached your quota, you can deactivate an existing instance before activating a new one (swap mechanism) or upgrade your plan.