System Configuration
Centralized configuration guide for Aevum Zenth internal systems, cross-division APIs, and deployment environments. All parameters support environment variable override.
Quick Start
Initialize your local development environment by cloning the monorepo and running the bootstrap script. Configuration files are version-controlled and environment-scoped.
# Clone the central configuration repository git clone https://git.aevumzenth.internal/config-core.git cd config-core # Generate environment-specific defaults ./az-init.sh --env=development --division=all # Validate configuration integrity az-config validate --strict
Environment Profiles
Aevum Zenth systems support three primary deployment environments. Switch profiles using the AZ_ENV variable or tab selection below.
AZ_ENV=development AZ_API_BASE=http://localhost:8080/v4 AZ_DB_HOST=postgres-dev.zenth.internal AZ_LOG_LEVEL=debug AZ_DIVISION_MODE=hybrid AZ_SECRET_KEY=dev-key-rotate-daily
AZ_ENV=staging AZ_API_BASE=https://staging.api.aevumzenth.internal/v4 AZ_DB_HOST=postgres-staging.zenth.internal AZ_LOG_LEVEL=info AZ_DIVISION_MODE=isolated AZ_SECRET_KEY=staging-vault-ref:kv/engineering/az-secret
AZ_ENV=production AZ_API_BASE=https://api.aevumzenth.com/v4 AZ_DB_HOST=postgres-prod.zenth.internal AZ_LOG_LEVEL=warn AZ_DIVISION_MODE=production-cluster AZ_SECRET_KEY=vault-inject:prod/az-master-key
Configuration Parameters
Core environment variables required for cross-division communication and service mesh routing.
| Parameter | Type | Default | Description | |
|---|---|---|---|---|
| AZ_ENV | string | development | Deployment environment profile | Required |
| AZ_API_BASE | url | - | Primary API gateway endpoint | Required |
| AZ_DIVISION_MODE | enum | hybrid | Module isolation strategy (hybrid/isolated/cluster) | |
| AZ_SECRET_KEY | string | - | JWT signing key for internal auth | Required |
| AZ_LOG_LEVEL | enum | info | Logging verbosity (debug/info/warn/error) | |
| AZ_DB_POOL_SIZE | int | 20 | Maximum database connections per worker | |
| AZ_RATE_LIMIT | int | 1000 | Requests per minute per API key | |
| AZ_CROSS_DIVISION | bool | true | Enable inter-division data sync |
Security & Authentication
All Aevum Zenth services enforce mTLS at the service mesh layer. Division-specific credentials must be rotated via the Vault integration.
Never commit AZ_SECRET_KEY or raw credentials to version control. Use the az-vault sync CLI to inject secrets at build time. Cross-division endpoints require valid OAuth2 client credentials with division-scoped claims.
# Rotate division-specific API keys az-auth rotate --division=aevum-energy --force # Verify mTLS handshakeaz-mesh verify --endpoint=internal.zenth.internal --tls-version=1.3