Connect your hosting business’s AWS account before offering DocumentDB databases through PD AWS DocumentDB. Each order uses that account to create a managed document-database cluster. The AWS access key authorises infrastructure management; it is separate from the database login used by an application.

Prepare the account

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

Review DocumentDB management, CloudWatch reads and EC2 security-group creation and ingress permissions separately. The module creates a firewall group during provisioning, so checking only database-read permission is insufficient. The AmazonRDSFullAccess policy includes database operations and metric reads, but not security-group creation or ingress changes. Have the administrator check any service-role prerequisites for first use as well.

Save the connection

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

Open PD Modules → PD AWS DocumentDB → Settings → Test Connection. Read what the connection test verifies before treating a passing result as proof that provisioning will succeed.

Check the offering

Confirm that the package uses the intended account and region. Plan private application access before accepting orders. When rotating credentials, verify the required dependent operations before retiring the previous pair. A passing read test does not establish write permissions, available capacity or a working database connection.

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