PUT Bucket consistency
Suggest changes
PDFs
The PUT Bucket consistency request allows you to specify the consistency level to apply to operations performed on a bucket.
The default consistency controls are set to guarantee read-after-write for newly created objects.
You have the s3:PutBucketConsistency permission, or be account root, to complete this operation.
Request
The x-ntap-sg-consistency parameter must contain one of the following values:
| Consistency control | Description |
|---|---|
all |
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. |
read-after-new-write |
(Default) Provides read-after-write consistency for new objects and eventual consistency for object updates. Offers high availability and data protection guarantees. Recommended for most cases. |
available |
Provides eventual consistency for both new objects and object updates. For S3 buckets, use only as required (for example, for a bucket that contains log values that are rarely read, or for HEAD or GET operations on keys that don't exist). Not supported for S3 FabricPool buckets. |
Note: In general, you should use the “read-after-new-write” consistency control value. If requests aren't working correctly, change the application client behavior if possible. Or, configure the client to specify the consistency control for each API request. Set the consistency control at the bucket level only as a last resort.
Request example
PUT /bucket?x-ntap-sg-consistency=strong-global HTTP/1.1 Date: date Authorization: authorization string Host: host