Regional Configuration

Reference guide for regional settings, data residency, and latency optimization in Sazabi projects.

Sazabi operates regional infrastructure to support data residency requirements and optimize latency. When you create a project, you select a region that determines where your data is stored and processed.

Available regions

Region	Location	Intake endpoint
`us-east-1`	US East (N. Virginia)	`otlp.us-east-1.intake.sazabi.com`
`eu-west-1`	EU West (Ireland)	`otlp.eu-west-1.intake.sazabi.com`

Additional regions are being added. Contact us if you need a region not listed here.

Choosing a region

When selecting a region for your project, consider:

Data residency requirements

If your organization has data residency requirements (GDPR, industry regulations, company policy), choose a region that satisfies those requirements:

EU data residency: Use eu-west-1 for data that must remain in the European Union
US data residency: Use us-east-1 for data that must remain in the United States

Latency optimization

For the best performance, choose a region close to your log sources:

Applications hosted in AWS us-east should use us-east-1
Applications hosted in AWS eu-west or other EU regions should use eu-west-1

Closer proximity reduces network latency for both log ingestion and Chat queries.

Multi-region considerations

If you operate in multiple regions:

Create separate projects for each region
Route logs from each region to its corresponding project
Use the project switcher in the dashboard to investigate region-specific issues

Regional endpoints

Each region has dedicated endpoints for log ingestion:

US East (`us-east-1`)

# OpenTelemetry endpoint
https://otlp.us-east-1.intake.sazabi.com/v1/logs

# HTTP ingestion
https://intake.us-east-1.sazabi.com/v1/logs

EU West (`eu-west-1`)

# OpenTelemetry endpoint
https://otlp.eu-west-1.intake.sazabi.com/v1/logs

# HTTP ingestion
https://intake.eu-west-1.sazabi.com/v1/logs

Configuring region during project creation

During project creation, select your preferred region from the dropdown. The region cannot be changed after the project is created.

Specify the region when creating a project:

sazabi projects create --name "production-eu" --region "eu-west-1"

If no region is specified, the default region (us-west-2) is used.

Include the region in your create project request:

curl -X POST "https://api.sazabi.com/v1/projects" \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "production-eu",
    "region": "eu-west-1"
  }'

Region limitations

A project's region cannot be changed after creation. To move data to a different region, create a new project in the desired region and update your data sources to send logs there.

Cross-region queries

Chat can only query data within a single project. If you have logs in multiple regional projects, you need to switch projects to investigate region-specific issues.

External backends

When using external backends, the Sazabi project region affects where queries are executed, but the data itself is stored in your external system. Choose a Sazabi region close to your external backend for optimal query performance.

Data residency compliance

Sazabi's regional architecture supports compliance with data residency regulations:

Regulation	Recommended region
GDPR (EU data)	`eu-west-1`
US-only requirements	`us-east-1`

For enterprise compliance requirements, contact us to discuss your specific needs.