Skip to content

Feature: Bucket Integrity Check

When to use

Use this diagnostic tool when you need to verify that selected buckets can be listed and that their objects can be reached with the current execution identity.

Prerequisites

  • The Manager feature policy bucket_integrity_check is not disabled, plus the per-user or inherited Manager tool right bucket_integrity_check.
  • S3 permissions to list the bucket and run HeadObject on the objects being checked.
  • S3 GetObject permission only when using GET body mode.

Before you start

Prefer HEAD only for the first diagnostic pass. Use GET body only when you intentionally want to read object data and accept the extra traffic.

Steps

  1. Open Manager > Tools > Bucket integrity and keep the intended execution context selected.
  2. Select one or more buckets to check.
  3. Choose HEAD only or GET body, then set parallelism, optional Since, optional Max MB per object, and All versions if noncurrent object versions must be checked.
  4. Run the check and monitor progress.
  5. Filter the result list by bucket, context, status, error state, object key, or error message.
  6. Expand a bucket result to review affected object details, including stage, key, version, and error message.

Start from the bucket list to filter and select the exact scope before running a check, especially when the active Manager context contains several buckets.

Manager bucket integrity page with filterable bucket selection before a check Manager bucket integrity page with filterable bucket selection before a check

Expected result

The report shows whether each bucket passed, completed with object errors, or failed during listing. The tool does not write to the database and does not persist historical runs.

You are done when

Each selected bucket has a final status, and any object-level failures include enough key, version, stage, and message detail to decide the next action.

If you do not see this action

Check the active Manager context, global feature setting, Manager tool access, and whether the selected context has bucket-management capability.

Limits / feature flags

Note

Manager visibility is controlled by the bucket_integrity_check feature policy and the per-user or inherited Manager tool right of the same name.

Warning

HEAD only is the default mode. It checks object metadata access through HeadObject and does not read object bodies.

Warning

GET body reads object data through GetObject. It can generate significant S3 traffic, latency, and backend load on large buckets.

Note

By default only latest object versions are checked. All versions checks object versions but skips delete markers.

Note

Max MB per object applies only to GET body mode. Leave it empty for a complete read.

Note

Bucket result details show up to 500 affected object errors per bucket. The per-bucket error counter remains the source of truth for totals.