Choose PD AWS S3’s quota mode according to the storage service you intend to offer. A measured quota is not an immediate byte-by-byte limit on every upload.

Distinguish the modes

Soft is the default: usage and notifications help you follow up, while uploads continue. In Hard mode, measured usage above the configured quota can pause uploads through the service’s AWS policy. Downloads and deleting remain available in that quota state so customers can free space.

Read-only suspension is different: it also blocks deletes. Disabled access is different again and can block downloads. A 403 response therefore needs the actual service state, not an assumption that every refusal means full storage.

Investigate a paused upload

1. Open the intended service’s Usage page and review its quota and measurement time.
2. Check the quota mode and current access state.
3. Review old versions and other buckets using the same service allowance.
4. Remove only data deliberately no longer needed, or arrange an intended quota upgrade.
5. Use Refresh and inspect the result when the page allows it.

Scheduled CloudWatch data is daily, while Refresh attempts a current count within its supported limits. Deleting a visible versioned file may not free the older stored versions.

Check the billing-platform policy

The usage integration can feed native service disk-usage fields. Review your intended native overage and suspension settings separately; measured usage alone is not proof that an invoice was generated.

After an upgrade, confirm the plan-change operation updated this existing service rather than only changing a default for future orders. Use the measurement guide if uploads remain paused after the intended change.

Allow for missing daily metrics

If CloudWatch has no data for a bucket, the module can use a bounded object/version walk as a fallback. That fallback can be accepted even when its listing was incomplete, so a completed Refresh or recent page update is not proof that every object and version was counted. Your hosting team and AWS administrator should compare the intended bucket set and actual storage before relying on an apparent space reduction or treating a quota-related access change as evidence of a complete measurement.

Check the quota and access mode

Your hosting team should compare this service’s stored allowance and Soft/Hard mode with the measurement source/time, actual access mode and original policy-update result. Review suspension separately. Check retained versions, other service buckets and incomplete fallback coverage before relying on an apparent space reduction; confirm a successful measurement and policy update after an intended deletion or plan change. Do not give out the host key, purge the service or change unrelated billing settings to diagnose an upload pause.

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