Slack Integration

What Slack can do

The integration has a deliberately narrow scope.

List non-removed RDS databases in the connected SnoozeDB organization.
Show each database identifier and a simplified running or stopped state.
Start one RDS database temporarily for 1, 3, or 5 hours.
Return control to the normal schedule when the temporary override expires.

Prerequisites and workspace access

A SnoozeDB owner or admin connects or reconnects Slack from Dashboard → Settings → Cloud integrations.

The Slack app requests the commands and chat:write scopes.

Slack workspace membership is the command boundary

After the workspace is connected, any member of that Slack workspace can list and temporarily start databases. They do not need a matching SnoozeDB account or organization role. Connect only a workspace whose membership is appropriate for this access.

Connect Slack

Select the SnoozeDB organization you want Slack to control.
Open Settings, then Cloud integrations.
Choose Connect Slack or Reconnect Slack.
Review the Slack workspace and requested permissions, then authorize the app.
Return to SnoozeDB and confirm the connected workspace name.

Slack commands

List databases

/snoozedb-list

The ephemeral response lists RDS identifiers from the connected organization. Removed resources are excluded, and state is simplified to running or stopped.

Choose a database

/snoozedb-start staging-db

Pass the exact RDS identifier. If nothing matches, use the list command. If several resources match, provide the complete identifier.

Start a database temporarily

After a unique match, Slack offers 1h, 3h, 5h, and Cancel. Choosing a duration starts the RDS instance and saves an override until the displayed expiry time. Normal scheduling resumes afterward.

Security and audit boundary

SnoozeDB verifies Slack request signatures before accepting commands or button interactions.
Start requests use the existing AWS role and External ID for the resource account.
Slack responses are ephemeral.
A successful start creates an automation log and a user activity entry with the Slack user ID and duration.
The activity entry is associated with the SnoozeDB user who installed the integration; its details identify the Slack actor.

Keep the wider audit trail

SnoozeDB Activity Logs complement but do not replace Slack audit logs or AWS CloudTrail.

Troubleshooting

Workspace not connected: reconnect Slack from the intended SnoozeDB organization.
No resources listed: verify the organization and run a SnoozeDB sync.
Database not found or several matches: run /snoozedb-list and copy the exact identifier.
Start failed: check SnoozeDB Activity Logs, AWS role permissions, and the current RDS state.
Slack settings unavailable: confirm the integration is enabled and that you are an owner or admin.