Resource Management

Synchronization

A sync refreshes resource status, tags, class, region, snapshots, and recommendations for the enabled modules and regions.

You can start a sync from the dashboard. While one is running, SnoozeDB disables additional sync requests. A later successful sync marks resources that no longer exist in AWS as removed.

Triage

The dashboard separates newly detected resources from resources you manage and resources protected from automation.

Status	Meaning	Scheduled
Managed resources	Managed resources follow their assigned schedule unless they are locked	Yes
To triage	To triage contains new resources waiting for your decision	No
Protected	Protected resources are excluded by your decision, a rule, or detected commitment coverage	No

Tag-based exclusion

You can exclude instances from automatic management via two mechanisms: AWS tags and organization rules.

Tags and organization rules are evaluated during synchronization. Matching resources appear as Protected and are not scheduled.

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.

Best practices

Always lock an instance before a planned maintenance operation. This prevents SnoozeDB from stopping it during a migration or backup in progress.

Quotas

Plan capacity counts active managed RDS databases only. EC2 scheduling requires a paid plan, but EC2 instances do not consume database capacity.

If you reach the RDS capacity limit, move a managed database out of the active set or change the workspace plan.