Review PD AWS S3’s retention and purge policy before terminating a storage service. Ending customer access and permanently deleting stored data are different actions.

Choose the policy before termination

Open PD AWS S3 → Settings and review Keep data after termination and Purging terminated data. A positive retention period leaves time to review recovery. Manual purge mode requires approval; Automatic mode pre-approves eligible deletion.

The shortest retention choice does not replace the separate approval policy. Conversely, automatic approval means the queue can delete eligible data without another per-service decision.

Inspect the terminated service

1. Use the intended platform termination or cancellation workflow with its module operation enabled.
2. Read the actual result in Activity.
3. Open Retention and inspect the service, stored inventory, countdown and approval state.
4. Use Hold when a recovery decision is outstanding.
5. Check the actual current state before taking further action.

Successful termination revokes the service credential and schedules retained storage for the selected policy. Retention keeps the existing bucket; it is not a separate backup copy. Independent lifecycle rules or authorised native changes can still affect its contents.

Decide recovery before purge begins

Recovery differs by billing platform, so use the platform-specific recovery guide. Once purge is in progress, some data may already have been deleted. Hold can pause future purge work, but it does not reconstruct removed objects.

Use the purge guide only when permanent deletion of the entire terminated service’s storage is intended.

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