Resource Management

Synchronization

A sync refreshes resource status, tags, class, region, snapshots, and recommendations. Full scans discover account-enabled AWS regions and scan the supported regions with up to four regions processed concurrently per stage. Region activation does not guarantee that the IAM role can read every service there. If region discovery is unavailable, the scan falls back to the supported regions in its requested scope.

Sync Now scans all supported account-enabled regions, including regions with no previously known resources. Dashboard auto-syncs refresh known regions. While a sync is running, additional sync requests are disabled. Resources absent from a successful regional inventory are marked as removed and hidden from the dashboard; failed or skipped inventories preserve existing resources.

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.

Add tags from SnoozeDB

Use the dashboard to add AWS tags individually or in a batch. For example, this tag protects a resource without an additional Settings rule:

In Resources scheduling, choose Add tags on a resource, or use the Add tags button to select several resources.
Enter up to ten unique key/value pairs. Existing values are kept; a different value for an existing key must be changed in AWS.
Choose Save to AWS and review the result for each resource. Production and Settings exclusions protect resources immediately.

snoozedb:enabled=false

Owners and admins can add tags, with MFA when required and an active workspace or valid trial. Update existing CloudFormation stacks with the latest template to grant tag addition permissions.

Supported targets are RDS databases, standalone EC2 instances, EKS clusters and managed node groups. EKS tags apply only to the selected target and are not copied to worker instances. This version adds tags; it does not edit or delete them.

If tagging or confirmation fails, run Sync Now to check AWS tags. A protective addition can leave a temporary lock until synchronization confirms the result. Removing an exclusion returns the resource to To triage without reactivating management.

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.

EKS management

The CloudFormation template grants AWS access to all current and future EKS clusters in the account. A sync discovers clusters even with no EC2 workers and adds new clusters to To triage. Choose Manage or Protect; later syncs keep that choice. Each managed cluster uses one unit of your plan capacity.

Individual EC2 actions and schedules are disabled for EKS workers. Manage and Protect apply to the cluster. Production tags and exclusions from Settings remain blocking.

EKS management

Hibernation scales managed node groups to zero for dev/test clusters, through your CloudFormation role and with no Kubernetes drain. Fargate, Auto Mode, Karpenter or other nodes outside managed node groups, and clusters managed by a platform are not eligible. The guide lists the requirements and explains recovery after a failed operation.

Quotas

Plan capacity counts managed RDS databases and managed EKS clusters, one unit each. EC2 scheduling and EKS hibernation require a paid plan; EC2 instances do not consume capacity.

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