Changing the consistency level

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

Before you begin

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 Default consistency level for your buckets. If the default consistency level does not meet the client application's availability or consistency 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.


  1. Click S3 > Buckets.

    screenshot showing the S3 menu
  2. Select a bucket from the list.
  3. Click Configure Consistency Level.

    screenshot showing user selecting Configure Consistency level
  4. Select a consistency level for operations performed on the objects in this bucket.

    screenshot showing dialog box to edit the bucket conistency level
    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.
    Default (read-after-write for new) Provides read-after-write consistency for new objects and eventual consistency for object updates. Offers high availability, and data protection guarantees. Matches AWS S3 consistency guarantees.
    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 Default consistency level, but only provides eventual consistency for HEAD operations. Offers higher availability for HEAD operations than Default 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.
  5. Click Save.