Home / AWS / Fix AWS RDS Instance Unavailable

AWS

Fix AWS RDS Instance Unavailable

Resolve RDS instance unavailability by diagnosing storage issues, failover status, maintenance operations, and connectivity problems.

Published: Apr 2, 20266 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

Introduction

RDS instances can become unavailable due to storage exhaustion, hardware failures, maintenance operations, or network issues. When unavailable, applications can't connect to the database, causing service outages.

Symptoms

Connection refused:

```bash $ psql -h my-db.xyz.region.rds.amazonaws.com -U admin -d mydb

psql: could not connect to server: Connection refused ```

Instance status not available:

```bash $ aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].[DBInstanceStatus,StatusInfos]'

[["stopped", null]] # Or "creating", "deleting", "modifying", "upgrading" ```

Storage full error:

bash

ERROR: database is not accepting commands to avoid versioning conflicts
HINT: Stop the postmaster and vacuum in read-only mode.

Application connection error:

bash

FATAL: the database system is starting up
FATAL: remaining connection slots are reserved

Common Causes

1.Storage full - No space for operations, database goes read-only or stops
2.Instance stopped - Manually stopped or stopped due to inactivity
3.Maintenance in progress - Upgrade or patching operation
4.Failover in progress - Multi-AZ failover happening
5.Hardware failure - Underlying hardware issue
6.Network connectivity - VPC, subnet, or security group issues
7.Parameter group issues - Invalid configuration preventing startup

Step-by-Step Fix

1.Check logs for specific error messages
2.Verify configuration settings
3.Test network connectivity
4.Review recent changes
5.Apply corrective action
6.Verify the fix

Step 1: Check Instance Status

```bash # Get current status aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].[DBInstanceStatus,DBInstanceClass,Engine,EngineVersion]'

# Status values: # - available: Normal operation # - creating: Instance being created # - modifying: Configuration change in progress # - upgrading: Engine upgrade in progress # - rebooting: Instance rebooting # - stopped: Instance stopped # - stopping: Instance being stopped # - deleting: Instance being deleted ```

Step 2: Check for Storage Issues

```bash # Check storage usage aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].[AllocatedStorage,MaxAllocatedStorage]'

# Check CloudWatch for storage metrics aws cloudwatch get-metric-statistics \ --namespace AWS/RDS \ --metric-name FreeStorageSpace \ --dimensions Name=DBInstanceIdentifier,Value=my-db \ --statistics Minimum \ --period 300

# If FreeStorageSpace < 5GB, instance may have issues ```

Increase storage if needed:

bash

aws rds modify-db-instance \
  --db-instance-identifier my-db \
  --allocated-storage 100 \
  --apply-immediately

Step 3: Start Stopped Instance

```bash # If instance is stopped aws rds start-db-instance --db-instance-identifier my-db

# Wait for it to become available aws rds wait db-instance-available --db-instance-identifier my-db ```

Step 4: Check for Pending Maintenance

```bash # Check pending maintenance actions aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].PendingModifiedValues'

# Check maintenance window aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].[PreferredMaintenanceWindow,PendingMaintenanceActions]'

# Apply pending maintenance aws rds apply-pending-maintenance-action \ --resource-identifier arn:aws:rds:region:account:db:my-db \ --apply-action system-update \ --opt-in-type immediate ```

Step 5: Check for Multi-AZ Failover

```bash # Check if Multi-AZ aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].MultiAZ'

# Check events for failover aws rds describe-events \ --source-identifier my-db \ --source-type db-instance \ --start-time $(date -d '1 hour ago' -u +%Y-%m-%dT%H:%M:%SZ)

# Look for "Multi-AZ instance failover" events ```

Step 6: Check Error Logs

```bash # Download error log aws rds download-db-log-file-portion \ --db-instance-identifier my-db \ --log-file-name error/postgresql.log \ --output text | tail -100

# Or for MySQL aws rds download-db-log-file-portion \ --db-instance-identifier my-db \ --log-file-name error/mysql-error-running.log \ --output text | tail -100

# Common errors: # - "disk full": Storage exhausted # - "too many connections": Connection limit # - "out of memory": Memory exhaustion ```

Step 7: Verify Network Connectivity

```bash # Check VPC configuration aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].[DBSubnetGroup.VpcId,DBSubnetGroup.Subnets[*].SubnetIdentifier]'

# Check security groups aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].VpcSecurityGroups[*].[VpcSecurityGroupId,Status]'

# Verify security group allows your IP aws ec2 describe-security-groups --group-ids sg-12345 \ --query 'SecurityGroups[*].IpPermissions[*].[FromPort,IpRanges[*].CidrIp]'

# Test connectivity telnet my-db.xyz.region.rds.amazonaws.com 5432 nc -zv my-db.xyz.region.rds.amazonaws.com 5432 ```

Step 8: Check Parameter Group Issues

```bash # Check parameter group status aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].DBParameterGroups[*].[DBParameterGroupName,ParameterApplyStatus]'

# Status values: # - in-sync: Parameters applied # - pending-reboot: Static parameters need reboot # - applying: Parameters being applied

# Reboot to apply pending parameters aws rds reboot-db-instance --db-instance-identifier my-db ```

Step 9: Check Instance Class and Resources

```bash # Check instance class aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].DBInstanceClass'

# Check CPU and memory aws cloudwatch get-metric-statistics \ --namespace AWS/RDS \ --metric-name CPUUtilization \ --dimensions Name=DBInstanceIdentifier,Value=my-db \ --statistics Maximum \ --period 300

# High CPU could indicate resource exhaustion ```

Step 10: Contact AWS Support for Hardware Issues

```bash # If instance shows hardware-related status aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].StatusInfos[*].[Status,StatusType,Message]'

# Hardware issues show messages like: # - "Hardware failure" # - "Storage failure" # Contact AWS Support for hardware replacement ```

Recovery Actions

Status	Action
stopped	`aws rds start-db-instance`
storage-full	Increase allocated storage
modifying	Wait for modification to complete
upgrading	Wait for upgrade to complete
rebooting	Wait for reboot to complete
hardware failure	Contact AWS Support
network issue	Fix security groups/VPC

Verification

```bash # Check instance is available aws rds describe-db-instances --db-instance-identifier my-db \ --query 'DBInstances[*].DBInstanceStatus'

# Should return: "available"

# Test database connection psql -h my-db.xyz.region.rds.amazonaws.com -U admin -d mydb -c "SELECT 1"

# Should return: 1

# Check CloudWatch metrics aws cloudwatch get-metric-statistics \ --namespace AWS/RDS \ --metric-name DatabaseConnections \ --dimensions Name=DBInstanceIdentifier,Value=my-db \ --statistics Sum \ --period 60 ```

[Fix AWS RDS Connection Limit Exceeded](/articles/fix-aws-rds-connection-limit-exceeded)
[Fix AWS RDS Read Replica Lag High](/articles/fix-aws-rds-read-replica-lag-high)
[Fix AWS RDS Aurora Failover Slow](/articles/fix-aws-rds-aurora-failover-slow)

[AWS troubleshooting: Fix IAM Permission Denied - Complete Tro](fix-iam-permission-denied)
[AWS cloud troubleshooting: AWS ACM Certificate Pending Validation Because the](aws-acm-certificate-pending-validation-wrong-route53-zone)
[AWS cloud troubleshooting: AWS ALB Returns 502 Because the Target Closed the ](aws-alb-502-target-closed-connection-keepalive-timeout-mismatch)
[AWS cloud troubleshooting: Fix AWS ALB CreateListener TargetGroupNotFound Err](aws-alb-createlistener-targetgroupnotfound)
[AWS cloud troubleshooting: Fix Aws Alb Lambda 502 Bad Gateway Issue in AWS](aws-alb-lambda-502-bad-gateway)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

AWS RDS Instance Unavailable AWS RDS Instance Unavailable AWS AWS RDS Instance Unavailable troubleshooting AWS RDS Instance Unavailable fix Resolve RDS instance unavailability by diagnosing storage issues, failover status, maintenance operations, and connectivity problems AWS Resolve RDS instance unavailability by diagnosing storage issues, failover status, maintenance operations, and connectivity problems

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

AWS Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this aws-errors troubleshooting guide applies to my situation?

This guide is designed for aws-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these aws-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of aws-errors issue?

Most aws-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this aws-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for aws-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Apr 2, 2026

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

Fix AWS RDS Instance Unavailable

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Instance Status

Step 2: Check for Storage Issues

Step 3: Start Stopped Instance

Step 4: Check for Pending Maintenance

Step 5: Check for Multi-AZ Failover

Step 6: Check Error Logs

Step 7: Verify Network Connectivity

Step 8: Check Parameter Group Issues

Step 9: Check Instance Class and Resources

Step 10: Contact AWS Support for Hardware Issues

Recovery Actions

Verification

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

AWS Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

Fix AWS RDS Instance Unavailable

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Instance Status

Step 2: Check for Storage Issues

Step 3: Start Stopped Instance

Step 4: Check for Pending Maintenance

Step 5: Check for Multi-AZ Failover

Step 6: Check Error Logs

Step 7: Verify Network Connectivity

Step 8: Check Parameter Group Issues

Step 9: Check Instance Class and Resources

Step 10: Contact AWS Support for Hardware Issues

Recovery Actions

Verification

Related Issues

Related Articles

People also search for

Share this guide

More AWS Troubleshooting Guides

Browse Guides from Other Categories

AWS Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading