Why Does My RDS Instance Become Faulty After Its Database Port Is Changed?
Symptom
- The DB instance is in Faulty state after the original database port is changed.
- The DB instance cannot be connected using the new database port.
Possible Causes
The submitted database port is occupied.
Procedure
- If the database port is changed successfully, the previous change failed because the submitted database port was occupied.
- If the original database port still fails to be changed, contact technical support.
Parent topic: Capacity Expansion and Specification Change
- Symptom
- Possible Causes
- Procedure