Jitera requires object storage for file uploads, generated code artifacts, and project exports. Supported providers are AWS S3, Azure Blob Storage, and MinIO (S3-compatible).Documentation Index
Fetch the complete documentation index at: https://docs.jitera.ai/llms.txt
Use this file to discover all available pages before exploring further.
Storage Provider Comparison
| Feature | AWS S3 | Azure Blob | MinIO |
|---|---|---|---|
| Managed Service | Yes | Yes | Self-hosted |
| High Availability | Built-in | Built-in | Distributed mode |
| Cost | Pay per use | Pay per use | Infrastructure only |
| Air-gapped Support | No | No | Yes |
| Setup Complexity | Low | Low | Medium |
| Maintenance | None | None | Required |
Recommendations
- AWS EKS: Use AWS S3 — see AWS EKS Installation
- Azure AKS: Use Azure Blob Storage — see Azure AKS Installation
- On-premises: Use MinIO in distributed mode — see On-premises Installation
- Air-gapped: Use MinIO (only option) — see On-premises Installation
Storage Requirements
Buckets / Containers
Jitera requires 4 storage locations — called buckets (S3/MinIO) or containers (Azure):| Helm Key (S3/MinIO) | Helm Key (Azure) | Purpose | Access |
|---|---|---|---|
storage.secret.aws.AWS_BUCKET | storage.secret.azure.CONTAINER | Default storage for file uploads and automation service | Private |
storage.secret.aws.AWS_PUBLIC_BUCKET | storage.secret.azure.PUBLIC_CONTAINER | Public assets (images, documents) | Public read |
storage.secret.aws.AWS_EXPORT_PROJECT_BUCKET | storage.secret.azure.EXPORT_PROJECT_CONTAINER | Project exports and backups | Private |
storage.secret.aws.AWS_ULTRON_BUCKET | storage.secret.azure.ULTRON_CONTAINER | AI service storage (embeddings, documents) | Private |
The
storage.secret.aws.* keys are used for both AWS S3 and MinIO configurations. For MinIO, replace aws with minio in the path (e.g., storage.secret.minio.AWS_BUCKET).CORS Configuration
Two storage locations require CORS to support cross-origin browser requests:- Default bucket/container — The frontend uploads files directly to object storage using presigned URLs (browser
PUT) - Public bucket/container — The document/folder export feature downloads images via JavaScript
fetch()to package them into ZIP files (browserGET)
OPTIONS preflight requests automatically when CORS is configured — you only need to specify the actual data methods.
Default bucket/container
| Setting | Value |
|---|---|
| AllowedOrigins | Your Jitera domain including subdomains (e.g. https://*.example.com) — covers both the main domain and chat domain |
| AllowedMethods | GET, PUT, POST, DELETE, HEAD |
| AllowedHeaders | * |
| ExposedHeaders | ETag |
| MaxAgeSeconds | 3000 |
Public bucket/container
| Setting | Value |
|---|---|
| AllowedOrigins | Your Jitera domain including subdomains (e.g. https://*.example.com) |
| AllowedMethods | GET |
| AllowedHeaders | * |
| MaxAgeSeconds | 3600 |
Without CORS on the public bucket/container, the application still functions — images display correctly in the editor and PDF exports work. Only client-side document/folder export to ZIP will be affected, with images silently omitted from the archive.
Related Documentation
AWS EKS Deployment
Complete AWS deployment guide
Azure AKS Deployment
Complete Azure deployment guide
On-premises Deployment
On-premises deployment guide
Troubleshooting
Common issues and solutions