Configure the Fileupload Connector¶

Caution - do not turn off

Do not deactivate the Fileupload (scratch) connector. Other connectors will not work otherwise!

The Fileupload (scratch) connector represents My Documents in the user interface. After the installation, the connector is already activated. To ensure this has been done correctly and to specify the connection keys, execute the following steps.

In SEAL Operator, export the complete configuration of SEAL Operator to a YAML file in order to ensure that the current configuration settings are used.
```
operator config export <filename>.yml --insecure
```
Edit the exported file <filename>.yml.

In the section of the Fileupload (scratch) connector, check if cstatus is set to on.

operator:
  connectors:
  ...
    scratch:
      cstatus: 'on'
      serviceName: operator-fileupload
      url: 'https://localhost:3009'
  ...

In the env section, specify the following keys for the seal-operator-fileupload service:
```
env:
  service:
    ...
    operator-fileupload:
      tag:
        any:
          MONGO_FILEUPLOAD_URL: 'mongodb://<mongodb_server>:27017/operator-fileupload'
    ...
```
Literature - keys

For further information about available keys, refer to the Key Reference.

Hint - AWS S3 as file storage

AWS S3 can be used for storing large files contents instead of MongoDB. For more information, refer to Connect S3.

Recommendation – large files and high‑throughput scenarios¶

There is no hard product limit for the maximum file size enforced by SEAL Operator itself. For scenarios that must handle very large files (for example, multi‑GB uploads) or a high number of concurrent uploads, we recommend using a Simple Storage Service (S3) backend for storing file contents instead of MongoDB. For details on how to configure S3, refer to:

– Linux: Simple Storage Service (S3) – Windows:Simple Storage Service (S3)

Save the file.

Re-import it to Consul.

operator config import <filename>.yml --insecure

Next Step¶

Continue with: Connect a Backend System