2501 uses three configuration files, all generated by theDocumentation Index
Fetch the complete documentation index at: https://docs.2501.ai/llms.txt
Use this file to discover all available pages before exploring further.
init command with sensible defaults and documentation.
Configuration Files Overview
| File | Purpose |
|---|---|
2501.yaml | Main deployment configuration (registry, services, resources) |
env.engine | Environment variables for the 2501 Engine |
env.command-center | Environment variables for the Command Center UI |
2501.yaml
The main configuration file controls:- Registry - 2501 private ECR registry URL and authentication
- Deploy - Target platform, image tag, stack name
- Engine - Port, replicas, resource limits
- Command Center - Port, replicas, resource limits
- PostgreSQL - Optional managed database (experiments only)
- Swarm - Network and update strategy settings
The generated
2501.yaml file includes inline comments documenting all available options and their defaults.Registry Types
| Type | Description |
|---|---|
ecr-login | AWS ECR with credential helper. Required because ECR tokens expire every 12 hours, and 2501 needs to pull fresh images when launching new agents. |
generic | Standard Docker registry with username/password |
env.engine
Environment variables for the 2501 Engine service, including:- Database connection (required)
- Security keys (auto-generated)
- LLM provider API keys
- Optional integrations (Redis, Elasticsearch, Vault, AWS)
env.command-center
Environment variables for the Command Center UI, including:- Database connection
- Engine connection URL and API key
- Authentication secrets (auto-generated)
- Base URL configuration
Generating Configuration
Use theinit command to generate all configuration files:

