Not able to start RDS Instance - Stopped temporarily

It sounds like you're experiencing an issue with starting your RDS instance that was previously stopped. Here are some steps you can take to troubleshoot and resolve this issue:

1. Double-check the instance status: Sometimes the console may not immediately reflect the current status. Try refreshing the page after a few minutes to see if the status updates.

2. Use the AWS CLI: You can use the AWS Command Line Interface to get more detailed information about your instance status. Run the following command, replacing "your-instance-name" with your actual RDS instance identifier:

   aws rds describe-db-instances --db-instance-identifier your-instance-name | grep DBInstanceStatus

This will give you the current status of your instance.

3. Start the instance using AWS CLI: If the console button isn't working, try starting the instance using the CLI:

   aws rds start-db-instance --db-instance-identifier your-instance-name

4. Check for underlying issues: There might be problems preventing the instance from starting. These could include:

   • Issues with the associated KMS key if your instance is encrypted
   • Problems with the VPC or security group configurations
   • Insufficient capacity in the Availability Zone

5. Check CloudWatch logs: If you have enabled CloudWatch logs for your RDS instance, review them for any error messages that might explain why the instance isn't starting.

6. Verify account status: Ensure that your AWS account is active and in good standing, as account issues can sometimes prevent resources from starting.

If none of these steps resolve the issue, you may need to contact AWS Support for further assistance. They can provide more detailed diagnostics and help resolve any underlying problems preventing your RDS instance from starting.
Sources
Starting an Amazon RDS DB instance that was previously stopped - Amazon Relational Database Service
Why can't I access my RDS? | AWS re:Post