Use the billing service’s normal module suspension controls when restricting a PD MinIO S3 service. Review the configured access policy first; suspension keeps stored files but changes what its credential can do.

Choose the intended suspension behaviour

Open PD MinIO S3 → Settings and review When a service is suspended. Read-only keeps ordinary downloads available while blocking writes and deletes. Disabled blocks storage authentication or access. Check how a global setting affects the services you manage before changing it.

Verify the actual restriction

1. Identify the intended billing service and its primary bucket.
2. Use its supported module suspension action.
3. Inspect Activity and Clients & Storage for the result.
4. Verify the service’s actual access mode separately from the billing status.

A failed provider request is not proof the restriction took effect. Do not repeat blindly if the original outcome is uncertain, and do not delete a bucket or key as a substitute for normal suspension.

Check restoration against quota

Use the service’s supported module unsuspension action when the account issue is resolved. An over-hard-quota service can return to the quota-locked policy instead of unrestricted read/write. Inspect the latest measurement and quota checks before describing uploads as restored.

Suspension does not start termination retention, move objects or restore previously deleted data. If the service was cancelled or terminated, use the retained-data recovery guide rather than unsuspending an unrelated billing record.

Retain the service reference, chosen mode, original action time and redacted result while your hosting team checks a discrepancy, without credentials or customer files.

Check the resulting access mode

Your hosting team should compare the intended service and configured suspension mode with the original Activity result and actual storage access. Billing status alone does not establish whether the restriction or restoration reached MinIO. Review quota separately when uploads remain paused after unsuspension, and have your storage administrator inspect a discrepancy before changing credentials or repeating the action.

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