Use PD AWS S3 → Reconcile to compare configured AWS accounts with the module’s service records. This scan reports differences; it does not automatically delete or adopt the reported resources.

Run and read the scan

1. Confirm the intended AWS connections are configured.
2. Open Reconcile and run its scan.
3. Check the scan time, accounts checked, errors and warnings.
4. Review orphaned buckets, missing tracked buckets and unmatched module IAM users separately.
5. Compare a reported resource with the intended service and account before taking action.

The module filters orphan reporting to its naming scope. A resource outside that scope is not proof of a forgotten customer service, and a similarly named resource is not permission to remove it.

Separate absence from a failed read

Missing-bucket findings check tracked primary buckets; they do not establish that every additional bucket exists. Review required additional buckets separately with your AWS administrator.

A refused or incomplete provider listing cannot prove a bucket is gone. Inspect warnings and account scope before declaring data missing. Read actual provider state through the responsible administrator when needed.

An orphan report can follow interrupted provisioning or a changed account relationship. Do not immediately create another service or delete the unmatched IAM user; first establish which resource is still serving an application.

Keep repair deliberate

The scan is separate from Retention approval and from native AWS deletion. It cannot recover purged objects or attach an arbitrary bucket to a new service automatically.

Retain the scan time, affected service, account and redacted finding while your hosting team checks its actual AWS resources. Exclude credentials, file contents and unrelated account inventories. Use the provisioning troubleshooting guide when the difference follows a failed setup.

Interpret the scan result

Your hosting team should compare the scan time, intended account, warnings/errors and exact finding with the original service and actual AWS resources. Your AWS administrator should distinguish an absent primary bucket, additional buckets, a refused listing and an unmatched module IAM user before taking action. A clean scan does not prove every additional bucket exists; an orphan or unmatched user is not permission to delete it.

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