Changing the consistency level

If you are using an S3 tenant, you can use the Tenant Manager or the Tenant Management API to change the consistency control for operations performed on the objects in S3
buckets.

Before you begin

You must be signed in to the Tenant Manager using a supported browser.

Users must belong to a user group that has the Manage All Containers or the Root Access permission. These permissions override the permissions settings in group or bucket policies.

About this task

Consistency level makes a trade-off between the availability of the
objects and the consistency of those objects across different Storage Nodes
and sites. In general, you should use the Read-after-new-write consistency level
for your buckets. If the Read-after-new-write consistency level does not meet the client application's requirements, you can change the consistency level by setting the bucket consistency level or by using the Consistency-Control header. The Consistency-Control header overrides the bucket consistency level.

Steps

Click S3 > Buckets.

Select a bucket from the list.

Click Configure Consistency Level.

Select a consistency level for operations performed on the objects in this bucket.

Consistency level

Description

All

Provides the highest guarantee of read-after-write consistency. All nodes
receive the data immediately, or the request will fail.

Strong-global

Guarantees read-after-write consistency for all
client requests across all sites.

Strong-site

Guarantees read-after-write consistency for all
client requests within a site.

Note: If your application attempts HEAD operations on keys that do not exist, set the Consistency Level to Available, unless you require AWS S3 consistency guarantees. Otherwise, a high number of 500 Internal Server errors can result if one or more Storage Nodes are unavailable.

Available (eventual consistency for HEAD operations)

Behaves the same as the
Read-after-new-write
consistency level, but only
provides eventual consistency for HEAD operations. Offers higher
availability for HEAD operations than
Read-after-new-write
if Storage
Nodes are unavailable. Differs from AWS S3 consistency guarantees
for HEAD operations only.

Weak

Provides eventual consistency and high availability, with minimal data protection guarantees, especially if a Storage Node fails or is unavailable. Suitable only for write-heavy workloads that require high availability, do not require read-after-write consistency, and can tolerate the potential loss of data if a node fails.