The appropriate consistency level is strong-global because the requirement explicitly applies to clients and object metadata across multiple StorageGRID sites. NetApp defines strong-global as providing read-after-write consistency for all client requests across all sites. Therefore, after an object is created or its metadata is changed, subsequent requests from any site receive a consistent view of that change.

strong-site is insufficient because its consistency guarantee applies only to client requests within a single site. A client accessing the bucket from another StorageGRID site could therefore fall outside the required site-wide consistency guarantee. read-after-new-write, which is the default and generally recommended setting, guarantees consistency for newly created objects but provides eventual consistency for object updates. Because the scenario requires immediate consistency following both new writes and changes, it does not meet the stated requirement. available provides eventual consistency for both new objects and updates and prioritizes availability rather than cross-site consistency.

Thus, among the available options, strong-global is specifically designed for workloads requiring globally consistent object and metadata visibility across a multisite StorageGRID deployment.

Reference topics: S3 Buckets → Bucket Consistency → Strong-global → Strong-site → Read-after-new-write → Metadata Distribution Across Sites