Regions and residency

Where ingest lands, where data rests, and how to pin a dataset to a jurisdiction.

Ingest is anycast: your events are accepted at the nearest point of presence, then written to the storage region the dataset is pinned to.

PoP	Location	Storage region available
`iad`	Ashburn, US	`us-east`
`pdx`	Portland, US	`us-west`
`fra`	Frankfurt, DE	`eu-central`
`lhr`	London, UK	`eu-west`
`sin`	Singapore	`ap-southeast`
`gru`	São Paulo, BR	`sa-east`

Pinning a dataset

Set region at creation. It is immutable afterwards — moving data across a jurisdiction boundary is a migration, not a setting.

cURL

curl -X POST https://api.logstreem.com/v1/datasets \
  -H "Authorization: Bearer $LOGSTREEM_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "name": "eu-customer-events", "region": "eu-central", "retention_days": 400 }'

Ingest crosses borders, storage does not

An event from a Singapore server destined for an eu-central dataset is accepted at sin and forwarded encrypted. If your policy forbids that transit, send directly to the regional ingest host — https://fra.ingest.logstreem.com.

PreviousRetention NextLimits