# No lifecycle management for temporarily stopped RDS instances Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/no-lifecycle-management-for-temporarily-stopped-rds-instances While stopping an RDS instance reduces runtime cost, AWS enforces a 7-day limit on stopped state. By: Shireen Maini Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # No Lifecycle Management for Temporarily Stopped RDS Instances The short version While stopping an RDS instance reduces runtime cost, AWS enforces a 7-day limit on stopped state. [Shireen Maini](https://www.linkedin.com/in/shireen-maini/) DevOps Team Lead @ BroadPeak Partners AWS service [AWS RDS](https://www.pointfive.co/efficiency-hub/cloud-services/aws-rds) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0097 Type Idle or Unused Resource ## Explanation Why the waste happens and who it affects. After this period, the instance is automatically restarted and resumes incurring compute charges - even if the database is still not needed. This creates waste in cases where teams intended to pause the environment but failed to manage its lifecycle beyond the 7-day window. Without proper automation or teardown workflows, stopped RDS instances silently become active and billable again. The best practice for long-term inactivity is to snapshot the database and delete the instance entirely. If the instance must remain available for fast recovery, automation should be in place to re-stop it upon restart. ## Billing model The pricing dimensions that drive this cost. RDS instances are billed based on: Instance runtime (per hour) Charged only while running Provisioned storage and snapshots Billed independently of instance state When an instance is restarted after 7 days without being actively used, runtime charges resume. ## How to detect 4 checks to find it in your estate. - Identify RDS instances that were restarted automatically after reaching the 7-day stop limit - Check for repeated stop/restart patterns without sustained usage - Review tags or naming patterns indicating temporary or paused projects - Engage with workload owners to determine whether reactivation was intentional or overlooked ## How to fix 5 ways to remove the waste. For projects on hold or long-term inactive environments: - Take a snapshot and delete the RDS instance to avoid all runtime charges - Restore from snapshot only when the environment is needed again If the instance must remain stopped for quick recovery: - Tag eligible instances and implement automation (e.g., AWS Step Functions or Lambda) to monitor for automatic restarts and re-stop them as needed - Ensure teams are aware of the 7-day stop limit and its cost implications - Consider integrating this logic into existing environment lifecycle tooling ## Documentation Vendor references for pricing and configuration. [Stopping an Amazon RDS DB instance temporarily](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_StopInstance.html) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS RDS CER-0299 ### [Orphaned RDS Backup Storage After Database Deletion](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-rds-backup-storage-after-database-deletion) An RDS database instance is deleted but its manual snapshots or retained backups remain. Unlike automated backups tied to a live instance, these backups persist independently and continue generating storage costs despite no longer... Databases - AWS RDS CER-0065 ### [Inactive RDS Instance](https://www.pointfive.co/efficiency-hub/inefficiencies/inactive-rds-instance) An RDS instance remains in the running state but is no longer actively serving application traffic. These instances may be remnants of retired applications, paused development environments, or workloads that were migrated elsewhere. If an... Databases - AWS RDS CER-0064 ### [Inactive RDS Cluster](https://www.pointfive.co/efficiency-hub/inefficiencies/inactive-rds-cluster) An RDS cluster remains provisioned but is no longer serving any workloads and has no active database connections. Unlike underutilized resources, these clusters are completely idle-showing no query activity, background processing, or usage... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.