Use the billing platform’s module suspension workflow to change storage access without intentionally deleting its files. Confirm the intended service and module-wide suspension policy first.

Review the configured access policy

Open PD AWS S3 → Settings → When a service is suspended. Read-only preserves downloads while blocking writes and deletes; Disabled blocks customer access. The setting describes an intended access change, not a data backup.

Apply and verify suspension

1. Identify the exact service and current state.
2. Use the platform’s normal suspend action with the module operation enabled.
3. Read the actual module result in Activity.
4. Check Clients & Storage for state and access mode.
5. Verify the intended customer access using a controlled operation.

Changing a billing status alone is not evidence that the provider-side action succeeded. Investigate the returned result before repeating an uncertain action.

Unsuspend deliberately

Use the platform’s normal unsuspend action and verify the result. If the service remains above a hard quota, unsuspension can restore downloads and deleting while leaving uploads paused. It does not automatically bypass quota policy.

Disabled access is expressed through inactive service keys; keys are not necessarily replaced by a suspension. Do not rotate keys repeatedly to repair the wrong service state.

Use the quota guide for an upload pause and the termination-retention guide when access has ended through termination rather than suspension.

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