---
title: Regions
description: Multi-region sending (sa-east-1, us-east-1, eu-west-1, ap-northeast-1), per-region MAIL FROM, and SNS→SQS events.
locale: en
---

# Regions

Envimaily sends via **AWS SES** in multiple regions. Each sending domain picks a region at creation (`POST /v1/domains` with `region`).

## Supported regions

| Region | Customer MAIL FROM | Platform example |
|--------|--------------------|------------------|
| `sa-east-1` (default) | `bounce` | `bounce.envimaily.com` |
| `us-east-1` | `bounce-us` | `bounce-us.envimaily.com` |
| `eu-west-1` | `bounce-eu` | `bounce-eu.envimaily.com` |
| `ap-northeast-1` | `bounce-ap` | `bounce-ap.envimaily.com` |

MAIL FROM **must** differ per region — the same MX hostname cannot serve two SES regions.

The dashboard shows MX/SPF pointing at `feedback-smtp.<region>.amazonses.com`.

## Feature flag

`SES_ENABLED_REGIONS` (default `sa-east-1`) lists regions offered in the UI/API. Others return `422 region_not_enabled`.

## Config sets

Names are **identical** in every region: `envimaily-pool-quarantine`, `envimaily-pool-standard`, `envimaily-pool-trusted`, `envimaily-dev-free`, etc. Warmup/reputation is tracked per `(tenant, region)`.

## Events

In each region, SNS topic `envimaily-ses-events` delivers to the single **sa-east-1** SQS queue (`envimaily-ses-events`). The `ses-events` worker handles events from any region (send tag `ses_region`).

## Credentials (Railway)

Per region (optional; otherwise global keys):

- `AWS_SES_ACCESS_KEY_ID_SA_EAST_1` / `AWS_SES_SECRET_ACCESS_KEY_SA_EAST_1`
- `AWS_SES_ACCESS_KEY_ID_US_EAST_1` / …
- Same pattern for `EU_WEST_1` and `AP_NORTHEAST_1`