As the hosting operator, you can guide your customers through using their PD AWS MySQL connection details to configure an application over TLS. The client-area steps below concern the customer’s database login, which is separate from your hosting business’s AWS connection.

Customer steps: collect the service details privately

1. Open the intended database service in the client area.
2. On Overview, confirm that the database is ready for connections.
3. Review the current host, port, database name and username.
4. Use the password reveal control when needed and store it privately.
5. Open the connection guidance and review the Amazon certificate-bundle link.

Do not assume a connection string includes the current password or that the same endpoint belongs to a replacement database. Keep filled-in connection details out of screenshots and tickets.

Configure TLS and network access

Configure the application with the exact database hostname and port, the appropriate CA bundle, TLS enabled and server identity verification. AWS’s RDS TLS guidance explains certificate validation; its Lightsail certificate guidance confirms that the RDS-labelled bundles also serve Lightsail managed databases.

Network reachability is a separate check. A private database needs an appropriate private route from the application. For public RDS access, review the service’s public-access setting and allowed application address; a firewall rule alone does not make a private endpoint publicly reachable. Lightsail has no module IP-firewall page.

Verify the application result

Test the required connection and a harmless application operation. Check that TLS and server verification are active. For a timeout, investigate routing and current service state; for authentication failure, compare the current database login and recent password changes.

Keep certificate verification enabled while your hosting team checks the hostname, appropriate CA bundle, network path and login. If the module displays the correct details but the application still cannot connect, investigate the application/TLS settings and actual database access separately from module provisioning.

See the PD AWS MySQL Blesta guide for related tasks, or explore PD AWS MySQL.