As the hosting operator, use PD AWS Oracle’s service state and Activity together when a customer database has not appeared or an operation seems unfinished. The billing record, the module’s recorded action and AWS readiness describe different stages.

Find the original service

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

Activity shows recent operations rather than a complete audit archive. If an earlier request is no longer listed, compare the original service reference, selected account and region with the database 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 the original request never reached AWS.

Distinguish a request from readiness

Queued or in-progress work still needs processing. A Done result can mean AWS accepted an operation while the database continues starting, changing or taking a snapshot. Check the actual resource state before telling the customer it is ready. A failure needs the recorded reason and intended configuration, rather than a guess based solely on the billing status.

Check paid-pending-service automation, the applicable client group and the running cron. When activating a pending service manually, staff must use the module if a database should be created. Payment by itself does not prove provider readiness.

Check the service and provider state

Review the account, region and plan selected for the original service. If AWS reports a specific refused permission or configuration requirement, check that requirement with your AWS administrator. If an operation is still in progress, follow that existing operation instead of creating another order for your customer.

Compare the recorded action with the database state in AWS. A request accepted by AWS and a database ready for application connections are different results. If the database is available but an application cannot connect, investigate its endpoint, network access and database login separately from provisioning.

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