Configuring External Storage and Backends

External Database (Gateway Controller)

The Gateway Controller defaults to an embedded SQLite database, which is limited to a single replica. For high-availability, multi-replica deployments, configure an external database as the shared storage backend. Both PostgreSQL and SQL Server are supported.

To configure the storage backend, update the config.toml:

PostgreSQLSQL Server

[controller.storage]
type = "postgres"

[controller.storage.postgres]
host = "postgres.example.com"
port = 5432
database = "gateway"
user = "gateway"
password = "your-postgres-password"
sslmode = "require" # disable, require, verify-ca, verify-full

[controller.storage]
type = "sqlserver"

[controller.storage.database]
driver = "sqlserver"
host = "sqlserver.example.com"
port = 1433
database = "gateway"
user = "gateway"
password = "your-sqlserver-password"

[controller.storage.database.options]
encrypt = "true" # disable, false, true, strict
trust_server_certificate = "false"

For the full list of storage configuration options for both databases, refer to the config template.

Redis (Gateway Runtime — Distributed Rate Limiting)

To enable distributed rate limiting across multiple Gateway Runtime instances, configure the rate limiting policy to use Redis as the backend in config.toml:

[policy_configurations.ratelimit_v1]
algorithm = "fixed-window"
backend = "redis"

[policy_configurations.ratelimit_v1.redis]
host = "redis.example.com"
port = 6379
password = "your-redis-password"

For the full list of Redis configuration options, refer to the Advanced Rate Limiting documentation.