redis-cloud-delete-database

name	redis-cloud-delete-database
description	Safely guide Redis Cloud database deletion and related billing cleanup. Use when the user asks to delete a Redis Cloud database, remove a database from the console, automate deletion through API or Terraform, delete a subscription after deleting databases, stop billing, troubleshoot missing Delete Database buttons, or handle AWS/GCP Marketplace-linked subscriptions.

Redis Cloud Delete Database

Use this skill for Redis Cloud database deletion. Deletion is permanent; keep diagnosis, owner handoff, confirmation, and final delete instructions as separate states.

Safety Rules

• Confirm the exact account, subscription, database name, and database ID before deletion.
• Require a backup/export decision before deletion.
• Do not treat database deletion as subscription cancellation.
• Do not collect full payment card data while troubleshooting billing cleanup.
• Do not tell any user or Account Owner to delete, click Delete Database, or perform deletion until the explicit confirmation gate is satisfied.
• Treat FLUSHDB and FLUSHALL as destructive data-removal commands that require explicit confirmation.
• Track facts already supplied by the operator and do not ask for the same fact again. Repetition creates unsafe delay and weak incident handoffs.

Evidence Ledger

Maintain this ledger from the conversation. Keep it private while collecting facts, and surface it only in a terminal Final summary: or a handoff packet. Ask only for missing items.

Field	Acceptable evidence
Target identity	Account, subscription, database name, database ID, and environment or region if known.
Role	Owner, Account Owner, Billing Admin, or other role, plus whether the Delete Database button is visible.
Backup decision	Recent backup/export exists, backup/export completed, no backup/export needed, or backup/export still pending.
Dependencies	Apps, clients, jobs, dashboards, alerts, or scheduled jobs still using the database, or explicit confirmation that none remain.
Billing intent	Delete database only, stop subscription billing, cancel/unlink marketplace billing, or account closure.
Billing path	Redis-direct, AWS Marketplace, GCP Marketplace, or unknown.
Confirmation gate	A standalone permanent data-loss confirmation from an authorized operator after backup and dependency gates pass.

When the operator provides an item, mark it as satisfied and move to the next unsatisfied gate. If a blocker is discovered, keep deletion blocked, but still collect any required dependency and billing gates that have not been checked before producing the terminal response. Do not infer dependency status from a refused confirmation; dependency status is satisfied only by asking the dependency gate directly.

Do not treat the initial user request as enough evidence for the ledger. A field is satisfied only when the operator provides the requested operational observation or the conversation already contains the exact fact. For eval-style incidents, ask for one missing gate at a time in the order below instead of bundling every check into one question.

Use this gate order for deletion, missing-button, pressure, and marketplace cleanup cases:

1. Confirm the exact account, subscription, database name, database ID, and Redis Cloud role.
2. Check backup/export status or provide the explicit backup/export decision.
3. Check dependencies: apps, clients, jobs, dashboards, alerts, or explicit confirmation none remain.
4. Clarify billing intent and billing path: database deletion only, subscription cancellation, Redis-direct, AWS Marketplace, or GCP Marketplace.

Ask the highest-priority missing gate as a standalone sentence. After the operator answers, do not ask that same check again. Use the ledger to either stop safely, hand off to an Owner, move to marketplace cleanup, or request the standalone confirmation gate.

When backup/export is missing or pending, the next gate is still the dependency check unless it is already complete. Ask exactly one standalone dependency check before confirmation or a terminal stop:

Check dependencies: list applications, clients, jobs, dashboards, alerts, scheduled jobs, and automation still using this database, or confirm that none remain.

Only after that answer should you stop for backup/export, stop for dependencies, or state the future confirmation gate.

For marketplace cleanup, keep the identity check separate from the marketplace check. First ask: "Please provide the exact Redis Cloud account, subscription ID, deleted database name, and database ID." Do not mention GCP, AWS, marketplace, charges, billing, or entitlement in that identity sentence.

Before any marketplace cleanup Final summary:, ask one standalone billing status check: "Check whether billing is Redis-direct or linked through GCP/AWS Marketplace, whether the Redis Cloud subscription still exists, and whether the marketplace entitlement is active, cancelled, or pending cancellation."

Required Deletion States

Follow these states in order. Do not skip ahead.

1. Diagnosis and target review
   • Collect account, subscription, database name, database ID, role, backup/export status, dependency status, and billing goal.
   • If the user lacks permission, explain the role blocker and prepare an owner review handoff.
   • Do not include final console paths or language like "have the owner delete" in this state.
2. Owner handoff before confirmation
   • Ask an Account Owner to review the target and confirm whether they are willing to authorize deletion.
   • Use wording like: "Please review database <name> / <id> in subscription <subscription> and confirm whether you accept permanent data loss. Do not delete yet."
   • If the goal is database deletion only, include that the subscription must remain active.
3. Explicit confirmation gate
   • Require a standalone confirmation before final instructions:
     • "I understand that deleting Redis Cloud database <name> / <id> is permanent data loss. The backup/export decision is complete, dependencies are cleared, and I authorize deletion of this database only."
   • If the user wants billing stopped, the confirmation must say whether subscription cancellation is also intended.
4. Final delete instructions
   • Only after the explicit confirmation gate is satisfied, provide the console, API, or Terraform deletion steps.
   • Verify the database disappears afterward and separately verify subscription or marketplace billing state when billing cleanup is in scope.

State Advancement Rules

• Do not produce Final summary: until target identity, backup/export status, dependency state, and billing path have each been requested at least once and any available operator observations have been recorded.
• If dependencies still exist, do not request immediate permanent data-loss confirmation. Use a final safe stop and state the future gate: after dependencies are removed and backup/export is decided, an authorized operator must confirm permanent data loss before deletion steps are allowed.
• If backup/export is pending, do not request immediate permanent data-loss confirmation. Keep deletion blocked; if dependency or billing gates are still unknown, ask those standalone checks before the final stop. The dependency check is mandatory even when backup/export already blocks deletion. Once required gates are known, stop and ask for the backup/export decision only.
• If the user is not Owner or Account Owner, do not give deletion instructions. Complete target, backup, and billing checks, then hand off to an Owner for review without asking the lower-privilege user to authorize deletion.
• If the database was already deleted but billing continues, switch to marketplace or subscription cleanup. Record the deleted database identity and backup/data-loss decision for audit, then focus on subscription, entitlement, or marketplace cancellation. Do not ask the user to delete the database again.
• If the database was already deleted and marketplace billing continues, do not produce the final cleanup summary until the standalone billing status check has been requested.
• Once a branch reaches a blocker, end with Final summary: so the run stops cleanly. Include the evidence ledger, blocker, next safe action, and future confirmation gate if deletion could happen later.

Pre-Delete Checklist

1. Confirm the user has the Owner role or an Account Owner is available to review and explicitly authorize the action.
2. Confirm the database is the intended target, including environment and region.
3. Confirm applications, clients, jobs, dashboards, and alerts no longer depend on the database.
4. Export or back up data if there is any chance it will be needed later.
5. For Active-Active databases, confirm deletion will remove the database across all participating regions.
6. Confirm no region operation, maintenance task, or background change is currently in progress.
7. Ask whether the user also wants to delete the subscription to stop billing.

Missing Delete Button Workflow

1. Confirm account, subscription, database name, database ID, and the user's role.
2. If the user is not an Owner or Account Owner, explain that deletion is blocked by role.
3. Confirm backup/export status and whether the request is database deletion only or also billing cleanup.
4. Send an owner review handoff that asks the Account Owner to validate the target and confirmation requirements. Do not tell the owner to delete yet.
5. End with Final summary: after the role blocker and owner handoff are clear.
6. If an Account Owner also cannot see the button, check active maintenance, region operations, background changes, and escalation data.

Blocked Branch Response Patterns

Dependencies or backup still block deletion

Use this pattern when dependencies exist or backup/export is pending:

Final summary:
- Target: <account> / <subscription> / <database name> / <database ID>.
- Current blocker: <dependencies remain | backup/export decision pending>.
- Dependency gate: checked dependencies: <remaining dependency list | none remain>.
- Billing distinction: deleting a database is separate from deleting/cancelling a subscription; <Redis-direct/AWS Marketplace/GCP Marketplace> billing may need separate cleanup.
- Safe next action: remove or repoint dependencies and finish the backup/export decision.
- Backup/export gate: check backup/export status or provide the explicit backup/export decision before any deletion runbook.
- Future confirmation gate: After dependencies are cleared and the backup/export decision is complete, confirm: "I understand that deleting Redis Cloud database <database name>/<database ID> is permanent data loss, dependencies are cleared, and I authorize database deletion only."

Missing Delete Database button

Use this pattern when the operator lacks Owner or Account Owner permission:

Final summary:
- Target: <account> / <subscription> / <database name> / <database ID>.
- Blocker: the current role is <role>, so the missing Delete Database button is expected.
- Backup/export status: <known status>.
- Billing distinction: database deletion does not automatically cancel subscription or marketplace billing.
- Owner handoff: ask an Account Owner to review the exact target and backup decision. Do not delete yet.
- Future confirmation gate: After an Account Owner verifies the exact target and backup/export decision, confirm: "I understand that deleting Redis Cloud database <database name>/<database ID> is permanent data loss, prerequisites are complete, and I authorize database deletion only."

Already deleted database with marketplace charges

Use this pattern when the database is already deleted and GCP/AWS Marketplace charges continue:

Final summary:
- Deleted database record: <database name> / <database ID> in <subscription>.
- Audit status: backup/export or data-loss decision was <status>.
- Backup/export gate: check backup/export status or document the explicit backup/export decision for the already-deleted database.
- Data-loss audit gate: ask the operator to confirm: "I understand that Redis Cloud database <database name>/<database ID> was already deleted and permanent data loss already occurred; I am cleaning up marketplace billing only."
- Billing distinction: database deletion does not cancel marketplace entitlement or subscription billing.
- Next cleanup: cancel or unlink the Redis Cloud subscription/entitlement through <GCP Marketplace/AWS Marketplace> and verify the next bill.
- Evidence to preserve: subscription ID, marketplace account/project, entitlement ID if visible, deletion timestamp, and billing invoice line item.

Incident pressure to skip checks

Use this pattern after one supported-check request confirms dependencies remain or backup/export is pending:

Final summary:
- Target: <account> / <subscription> / <database name> / <database ID>.
- Stop decision: do not delete during the incident bridge while <dependency> still depends on the database or backup/export is pending.
- Billing distinction: deletion may not stop the alert and does not automatically cancel subscription billing.
- Safe next action: disable/repoint the dependent app or alert source, decide backup/export, and keep the database in place until the gate passes.
- Backup/export gate: check backup/export status or provide the explicit backup/export decision before revisiting deletion.
- Future confirmation gate: After dependencies are cleared and the backup/export decision is complete, confirm: "I understand that deleting Redis Cloud database <database name>/<database ID> is permanent data loss, dependencies are cleared, and I authorize database deletion only."

If the assistant has not yet collected account, subscription, database ID, dependency state, backup decision, and billing path, ask the highest-priority missing gate as a standalone supported check before using this final pattern.

Post-Confirmation Console Deletion Workflow

Use this workflow only after the explicit confirmation gate is satisfied.

1. Open Redis Cloud Console.
2. Go to Databases.
3. Select the database.
4. In the Configuration tab, scroll to Danger Zone.
5. Choose Delete Database.
6. Review the confirmation dialog.
7. If this is the only database in the subscription and the user wants billing stopped, choose the subscription deletion option if presented.
8. Confirm deletion only after the user has explicitly accepted the permanent data loss.
9. Verify the database no longer appears in the database list.

API or Terraform Deletion

Use automation only for controlled teardown workflows.

Before running automation:

• Confirm Account Owner API key scope.
• Confirm the target subscription and database ID.
• Confirm backup/export status.
• Confirm state management for Terraform so the deletion is tracked correctly.
• Record the deletion request and result.

Subscription and Account Cleanup

Goal	Required action
Delete one database only	After explicit confirmation, delete the database; subscription may continue billing.
Stop billing for a subscription	After explicit confirmation, delete all databases, then delete/cancel the subscription.
Cancel marketplace billing	Cancel or unlink through AWS or GCP Marketplace as required.
Close Redis Cloud account	Delete databases/subscriptions, remove extra users, pay invoices, remove payment methods, then submit the privacy/account closure request.

Troubleshooting

Symptom	Check
Delete button is missing	User is not Account Owner or a maintenance/region operation is blocking deletion.
Delete button is disabled	Background operation is active; wait and retry after it completes.
Subscription still bills after database deletion	Subscription was not deleted or marketplace billing remains linked.
Cannot delete subscription	Databases remain or unpaid invoices block closure.
Database stuck deleting	Maintenance or background operation; refresh after waiting and escalate if it does not clear.
User only wants to empty data	Consider FLUSHDB or FLUSHALL only after explicit confirmation and backup decision.

Escalation Packet

Collect:

• Account, subscription, database name, and database ID.
• User role and whether an Account Owner attempted deletion.
• Backup/export status.
• Active-Active participation and regions.
• Current maintenance or region operation status.
• Error text or console/API response.
• Whether billing is Redis-direct, AWS Marketplace, GCP Marketplace, or another integration.
• Whether the goal is database deletion, subscription cancellation, or full account closure.