Connect the AWS account that will hold the databases you sell through PD AWS Oracle. The module uses Amazon RDS for Oracle. Your hosting business’s AWS access key is separate from the database login given to a customer.

Prepare the AWS connection

Install PD Modules, connect the account holding your licence, then install PD AWS Oracle from its Store. Ask the AWS administrator for a dedicated IAM user access key with the permissions needed for the database operations you intend to offer. Keep the key and secret out of customer applications, tickets and screenshots.

Review RDS management, CloudWatch reads and EC2 security-group permissions separately. The module creates a dedicated firewall group during provisioning: permission to create that group is needed before a first database can be created. The AmazonRDSFullAccess policy includes RDS operations and CloudWatch reads but does not grant security-group creation or ingress changes. The AWS administrator must review those additional actions too.

Save the account

Open Settings → Company → Modules, find PD AWS Oracle under Installed and choose Manage. Add an account with a recognisable name, Access Key ID and Secret Access Key, then save. A blank secret when editing an unchanged account retains its stored value. Select the intended account on the package.

Open PD Modules → PD AWS Oracle → Settings → Test Connection. Read what the module-panel test checks before treating a successful result as approval for provisioning.

Confirm the intended use

Check the package’s account association, region and database defaults before accepting orders. Real database creation can incur AWS charges. When rotating credentials, verify the intended dependent operations before retiring the old pair; a passing read test alone does not establish that every write is authorised.

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