# Tigris: CreateBucket silently falls back to Global for LocationConstraint=iad

## The problem

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.

## The verified fix

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