Find and export
your Amazon S3 data.

1. 1Use an account role with the required Storage Lens or bucket-metrics access.
2. 2Open S3 → Storage Lens → Dashboards and review total storage and object count.
3. 3For a bucket, inspect Metrics and the relevant storage classes.
4. 4For object-level detail, review an S3 Inventory report configured for current or all versions.

Report in GB, naming accounts, buckets and version scope. Add object counts and storage-class breakdowns where useful.

Describe the business content and oldest retained objects, including archived classes and any duplication with application inventories.

1. 1Use an object inventory as the checklist for the agreed buckets and versions.
2. 2Have the administrator restore archived objects that require retrieval before downloading.
3. 3Use aws s3 sync or another approved copy route for current objects.
4. 4For earlier versions or a larger controlled transfer, review S3 Batch Operations and version-specific manifests.

A normal aws s3 sync copies current versions. Retaining object history requires a version-aware plan.

Archive retrieval, requests and transfers can incur charges. Compare destination counts and sizes against the inventory.

Object stores can hold the original documents, images and event files behind a business application.

Object keys and metadata can connect those files to the records describing how they were used.

Choose bucket prefixes, versions and object types in scope, reviewing ownership and sensitive file content.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.