Decide how the application will reach its database before provisioning a PD AWS PostgreSQL service. RDS public accessibility, AWS routing and the allowed source addresses all affect connectivity; a correct database password cannot overcome a missing network path.

Choose the intended access model

Open the product’s Module Settings tab and review Publicly accessible. An application connecting over the internet needs an appropriate public endpoint and AWS network configuration. A private database needs an established private network path from the application. Leaving public access off does not build that path automatically.

AWS documents RDS VPC and subnet requirements. Ask the AWS administrator to check the region’s VPC, subnet group, routing and security-group rules for the intended application location. Public accessibility alone does not allow every source address or remove database authentication.

Review firewall prerequisites

For RDS, the module creates a dedicated security group for the database. Lightsail does not expose that per-IP firewall through this module; plan the intended application path and public-access choice separately. Its AWS connection needs permission to create and manage that group, in addition to RDS permissions. A connection test only performs an RDS read; it does not test group creation or a firewall change.

Allow the application’s intended source addresses through the supported controls and keep access as narrow as the application needs. Avoid opening the database to all addresses merely to diagnose a timeout. For an earlier network action with an uncertain result, compare its Activity entry with the actual rules in your AWS account before submitting another change. This access-planning guide does not replace checking the original operation.

Separate a timeout from a login refusal

Check the service’s current host, port and availability. A timeout calls for reviewing the network path and permitted source. An authentication refusal calls for checking the database username and current password privately. Keep AWS host credentials separate from the customer’s database login, and never paste either secret into a ticket.

See the PD AWS PostgreSQL WHMCS guide for related tasks, or explore PD AWS PostgreSQL.