Use PD AWS Oracle’s connection test to check whether the module can reach AWS and make an authenticated RDS read. The test creates no database, changes no firewall and does not place an order.

Run the module-panel test

1. Save the AWS connection using the account connection guide.
2. Open PD Modules → PD AWS Oracle → Settings.
3. Choose Test Connection and read the result.
4. Confirm separately that the package uses the intended account and region.

This module-panel test uses the first configured active account. It lists RDS instances in the test’s default region; it does not test every account or automatically follow every package’s region. A success confirms that read, rather than database creation, snapshot writes, password changes or firewall permissions.

Resolve a refused connection

For invalid credentials, ask the AWS administrator to check the saved key pair, accidental spaces and whether the key remains active. A secret cannot be retrieved from AWS after its creation; use an approved replacement pair if it was lost. For an access refusal, check the permission on the intended IAM user. A generic failure message is not proof that the credentials are the only possible cause: outbound HTTPS access and AWS availability also matter.

Keep the first provisioning check separate

Review the offering configuration and network prerequisites before a controlled first-service test. If an earlier attempt has an uncertain outcome, check its Activity and service state first. Repeated orders or repeated creation requests can make diagnosis harder and may create chargeable resources.

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