Why Are No RDS PostgreSQL Automated Backups Being Created?
A CloudOps engineer needs to ensure that an Amazon RDS for PostgreSQL DB instance has available backups. The DB instance has automated backups turned on with a backup retention period of 7 days. However, no automated backups for the DB instance have been created in the past month. What could be the cause of the lack of automated backups?
Community Insight
Tests whether you know RDS suppresses automated backups when DB storage is full; the trap is blaming a customer-managed S3 bucket or believing Multi-AZ or 30-day retention is mandatory.
Amazon RDS automated backups for a PostgreSQL DB instance stop being created when the instance enters the STORAGE_FULL state, so a 7-day retention setting alone does not guarantee backups. This page confirms why option B is the cause and explains why S3 capacity, Multi-AZ, and a 30-day retention are not requirements.
Learners often pick A and assume backups fill a customer-managed S3 bucket, but RDS automated backups are managed by the service and storage exhaustion on the DB instance is the actual blocker.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Amazon RDS normally creates automated backups during the daily backup window when automated backups are enabled with a nonzero retention period. However, if the DB instance has consumed its allocated storage and is in the STORAGE_FULL state, RDS cannot create those backups, which explains why no backups appeared during the past month despite a 7-day retention setting. Option B directly names the documented condition that blocks backup creation, and the lone community note from Bad_Mat also points to the same state: "The DB instance is in the STORAGE_FULL state". The retention period being shorter than 30 days is irrelevant because 7 days is a valid RDS retention setting.Why the Other Options Are Wrong
Option A is wrong because RDS automated backups are stored in Amazon S3 storage managed by RDS, not in a customer-owned S3 bucket that the engineer must monitor for free space. Option C is wrong because Multi-AZ is a high-availability deployment choice, not a prerequisite for automated backups; single-AZ RDS instances can and do have automated backups. Option D is wrong because RDS backup retention can be set within the supported range and does not need to be 30 days for backups to be created.Community Comment Notes
The visible community response from Bad_Mat selects option B and explicitly cites the STORAGE_FULL state as the cause. That aligns with the RDS behavior described in the question: backups are enabled and retention is valid, yet no backups have been produced for a month, which points to a storage condition on the DB instance rather than a configuration or Multi-AZ issue. No comment argues for the S3-bucket or 30-day-retention distractors, so the community note reinforces the storage-focused diagnosis.Official Reference
Exam Strategy
Map the symptom to RDS backup blockers before choosing: automated backups require free DB storage and a valid nonzero retention period. Multi-AZ and customer S3 bucket capacity are distractors, so eliminate them quickly and focus on the DB instance state.
Frequently Asked Questions
Why does STORAGE_FULL stop RDS automated backups?
When the DB instance exhausts its allocated storage, RDS cannot write the backup data and enters STORAGE_FULL, so automated backup creation is blocked until space is recovered or storage is increased.
Does RDS require Multi-AZ for automated backups?
No. Multi-AZ improves availability and failover, but single-AZ RDS instances can still have automated backups as long as retention is nonzero and the instance is healthy.
Related Analysis
Practice All SOA-C03 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SOA-C03 Practice Test →