Orphaned RDS Database Cannot Be Deleted - Stuck in Unmanageable State

Question

**Problem Summary:**
I have an orphaned RDS database (coachlens-dev-db) in us-east-1 that cannot be deleted or managed through normal AWS operations. The database appears to be stuck in an unmanageable state.

**Database Details:**
- Name: coachlens-dev-db
- Region: us-east-1
- Size: ~20GB
- Engine: [Your engine type - MySQL/PostgreSQL/etc.]

**What I've Tried:**
✅ AWS Console deletion - fails silently
✅ AWS CLI deletion commands - no response
✅ Checked for deletion protection - not enabled
✅ Verified IAM permissions - have full RDS access
✅ Successfully restored data from snapshots to new working database

**Current Impact:**
- Ongoing charges (~$2/day) for unusable database
- Cannot manage, modify, or delete through any normal AWS operations
- Appears to be an AWS infrastructure issue

**What I Need:**
- Force deletion of the stuck RDS instance
- Stop billing for the orphaned database
- Understanding of what caused this issue

**Additional Context:**
I've already successfully restored my data to a new working database, so this is purely about cleaning up the stuck/orphaned instance.

Has anyone encountered similar RDS instances that become "stuck" and unmanageable? What was the resolution?

re:Post Agent · Answer

When dealing with an RDS instance that's stuck in an unmanageable state, there are several approaches you can try before escalating to AWS Support.

First, check if the instance is in a "storage-full" state while also requiring an upgrade. This combination can create a deadlock where modifications fail because the storage is full, but you can't increase storage because it triggers the upgrade process. In such cases, try stopping the RDS instance first, then modify the deletion protection setting. Alternatively, try modifying the instance without selecting "Apply Immediately" to see if that works.

For RDS Custom instances, be aware that manually terminating the underlying EC2 instance or EBS volumes before properly deleting the RDS instance through the RDS service can cause the database to become stuck in an unmanageable state. This is because RDS needs to handle these resources in a specific order during deletion.

If your instance has deletion protection enabled but you can't disable it through normal means, try stopping the instance first before attempting to modify this setting.

Since you've already restored your data to a new working database, and if all the above approaches fail, your best course of action would be to contact AWS Support. They have internal tools to help resolve stuck resources that can't be managed through standard customer-facing interfaces. Be prepared to provide your account ID, the exact resource identifier (coachlens-dev-db), region (us-east-1), and a timeline of when the issue started and what actions preceded it.

AWS Support can also help address the billing concern for the orphaned instance, potentially providing credits for charges incurred while the resource was in an unmanageable state.  
**Sources**  
[Unable to delete RDS Instance Due to Delete Protection + Storage Full + Needs Upgrade | AWS re:Post](https://repost.aws/questions/QU2QCjT9NPTGuYF4UiC1uvww/unable-to-delete-rds-instance-due-to-delete-protection-storage-full-needs-upgrade)  
[Deleting an RDS Custom for Oracle DB instance - Amazon Relational Database Service](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/custom-managing.deleting.html)

Vishnu · Answer

Hi Harshal. It is possible sometimes that the RDS instance might be in a stuck state.

A service request should help you quickly on this. Did you raise it already?

Orphaned RDS Database Cannot Be Deleted - Stuck in Unmanageable State

Add your answer

Relevant content