[Solved] An RDS instance is unreachable despite correct security group rules. What else should you check? — Ans: Check if the RDS instance is in a private subnet without NAT gateway | AWS

AWS - RDS and Relational Databases

An RDS instance is unreachable despite correct security group rules. What else should you check?

AVerify if encryption is enabled

BCheck if the RDS instance is in a private subnet without NAT gateway

CConfirm the database engine version

DCheck if Multi-AZ is enabled

Step-by-Step Solution

Solution:

Step 1: Understand network accessibility
If the RDS instance is in a private subnet without proper routing or NAT, it may be unreachable.
Step 2: Recognize that encryption and engine version do not affect network reachability
Encryption and engine version do not block network access; Multi-AZ affects availability but not basic reachability.
Final Answer:
Check if the RDS instance is in a private subnet without NAT gateway -> Option B
Quick Check:
Private subnet without NAT can block access [OK]

Quick Trick: Private subnet without NAT blocks external access [OK]

Common Mistakes:

Master "RDS and Relational Databases" in AWS

9 interactive learning modes - each teaches the same concept differently

More AWS Quizzes

An RDS instance is unreachable despite correct security group rules. What else should you check?