As the hosting operator, compare the original service, its provider state and PD AWS DocumentDB’s Activity when your customer’s cluster provisioning appears unfinished. A billing record, an accepted operation and a usable database describe different stages. DocumentDB provisioning creates a cluster and a compute instance, so a cluster record alone does not establish application readiness.

Find the recorded request

1. Open PD Modules → PD AWS DocumentDB → Clients & Databases.
2. Identify the original service and intended AWS region.
3. Open Activity and match the service reference and action time.
4. Read the operation, status and redacted result before asking for another change.

Activity shows recent operations rather than a complete audit archive. If the original attempt is no longer listed, compare the service reference, selected account and region with the cluster and instance resources visible in your own AWS account. Record what exists and its state before requesting creation again; a missing recent entry alone does not establish that no earlier request reached AWS.

Check what is still pending

Queued or in-progress work needs processing. A Done entry can mean AWS accepted the request while the cluster or instance is still being created or changed. Check the resulting state and private connection path before telling the customer the database is ready.

Check paid-pending-services automation, applicable client-group settings and the running cron. Staff activating a pending service must use the module if a cluster should be created. Payment alone does not prove provider readiness.

Check cluster, compute and application access separately

Review the original account, region and plan with your AWS administrator. Compare the recorded request with both the intended cluster and its compute instance. Follow an existing operation still processing instead of placing another order to investigate it. A cluster record alone does not establish a usable application connection.

If the cluster and compute are available but the application cannot connect, investigate its private network path, endpoint and database login separately from resource creation. Record an AWS permission refusal or missing instance alongside the original module result rather than deleting the service as a reset.

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