Skip to main content
When building a workflow that involves file generation or file-based actions, Blink automatically stores these files in its default object storage. However, if you prefer to manage file storage within your own infrastructure, you have the option to configure and use a custom object storage solution instead.

​
Limitations​

For more information regarding limitations, please visit the Workflows Runtime Limitations section of our documentation.
  1. If you’re using Blink’s runner object storage, the maximum file size created by a step is limited to 500MB.
  2. If you configure your own object storage, there is no file size limit.

​
Object Storage Installation Guidelines​

We support all S3-compatible object storage, plus Microsoft Azure Blob Storage as a first-class backend. Currently, we provide detailed guidelines for AWS S3, Google Cloud Storage, and Azure Blob Storage. If you need assistance configuring S3-compatible object storage not covered in the documentation, please contact our support team for help.

AWS S3 object

Click here, to learn how to configure an AWS S3 object storage with a runner.

Google Cloud Storage

Click here, to learn how to configure Google Cloud Storage with a runner.

Azure Blob Storage

Click here, to learn how to configure Microsoft Azure Blob Storage with a runner.