Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Creating a bucket on Tigris with LocationConstraint=iad returns success but silently creates a Global bucket instead of an iad-region bucket. iad is not an AWS-defined location constraint, and Tigris was accepting it and discarding the placement requirement without any error. The risky behavior is the silent fallback: callers got success while their data-placement requirement was ignored.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Fixed and deployed by the Tigris team: the unsupported location constraint is no longer silently dropped. If you are pinning data placement, verify the bucket's actual region after creation rather than trusting the successful response.
Source: https://github.com/tigrisdata/storage/issues/218
Source: https://github.com/tigrisdata/storage/issues/218