Run logs and files are stored in the database by default, but you can switch to S3 later without any migration; for most cases, the database is enough.
It’s recommended to start with the database and switch to S3 if needed. After switching, expired files in the database will be deleted, and everything will be stored in S3. No manual migration is needed.
Environment Variables
| Variable | Description | Default Value | Example |
|---|
AP_FILE_STORAGE_LOCATION | The location to store files. Set to S3 for S3 storage. | DB | S3 |
AP_S3_ACCESS_KEY_ID | The access key ID for your S3-compatible storage service. Not required if AP_S3_USE_IRSA is true. | None | |
AP_S3_SECRET_ACCESS_KEY | The secret access key for your S3-compatible storage service. Not required if AP_S3_USE_IRSA is true. | None | |
AP_S3_BUCKET | The name of the S3 bucket to use for file storage. | None | |
AP_S3_ENDPOINT | The endpoint URL for your S3-compatible storage service. Not required if AWS_ENDPOINT_URL is set. | None | https://s3.amazonaws.com |
AP_S3_REGION | The region where your S3 bucket is located. Not required if AWS_REGION is set. | None | us-east-1 |
AP_S3_USE_SIGNED_URLS | It is used to route traffic to S3 directly. It should be enabled if the S3 bucket is public. | None | true |
AP_S3_USE_IRSA | Use IAM Role for Service Accounts (IRSA) to connect to S3. When true, AP_S3_ACCESS_KEY_ID and AP_S3_SECRET_ACCESS_KEY are not required. | None | true |
AP_MAX_FILE_SIZE_MB | The maximum allowed file size in megabytes for uploads including logs of flow runs. | 10 | 10 |
Friendly Tip #1: If the S3 bucket supports signed URLs but needs to be accessible over a public network, you can set AP_S3_USE_SIGNED_URLS to true to route traffic directly to S3 and reduce heavy traffic on your API server.
