Configuring access to MinIO service in S3-compatible mode in the community edition of n8n is ineffective

Questions
1

I would like to consult: Does the community edition of n8n support enabling S3 storage configuration? I have locally deployed n8n v2.2.4 and also deployed the latest MinIO community edition. However, after adding S3-related environment variables in n8n’s environment configuration, n8n fails to start normally. Checking the logs, the main error message is ‘S3 binary data storage requires a valid license’. Does this mean that the community edition of n8n does not support the S3 storage mode? How can I resolve this issue?

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

You will need an Enterprise license key for external storage. If your license key expires and you remain on S3 mode, the instance will be able to read from, but not write to, the S3 bucket.

I believe you can ‘manually’ configure your workflow to upload whatever you need to an s3 bucket. AWS, r2 cloudflare, backblaze etc.

Yeah, requires license.

3

Hi! Unfortunately, accessing S3 or S3-compatible storage requires an Enterprise license.

4

Hi @Xiaohu !

The Community Edition does not support S3 or S3-compatible storage as the global binary data backend. To proceed, you have two options:

A)Remove the S3-related environment variables and keep using the default local filesystem for binary data (fully supported in Community Edition).
B) Keep Community Edition and upload files to S3/MinIO manually inside your workflows (for example using the HTTP Request node or an S3-compatible API), instead of configuring S3 as the global storage backend.