Skip to content
LogScale Self-Hosted Deployment
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

### MinIO

You can use MinIO as a replacement for Amazon S3 for both S3 Archiving and Bucket Storage.

Follow these guides, and remember to set the endpoint base for the features you wish to use MinIO with to make sure your data goes to your local instance of MinIO rather than Amazon S3 by default.

ini

    S3_ARCHIVING_ENDPOINT_BASE=http://my-own-s3:9000
    S3_STORAGE_ENDPOINT_BASE=http://my-own-s3:9000
    S3_EXPORT_ENDPOINT_BASE=http://my-own-s3:9000

For LogScale's bucket storage to work properly with MinIO, set `BUCKET_STORAGE_IGNORE_ETAG_UPLOAD` equal to `true` in your configuration, to disable checksum matching while uploading the file; however the file integrity is still ensured.

You also need to set the access style to use the path style for the S3 features you wish to use MinIO with.

ini

    # Set path style access for the S3 archiving feature
    S3_ARCHIVING_PATH_STYLE_ACCESS=true

    # Set path style access for S3 bucket storage
    S3_STORAGE_PATH_STYLE_ACCESS=true

    # Set path style access for the export search to S3 feature
    S3_EXPORT_PATH_STYLE_ACCESS=true

MinIO in its default mode doesn't use MD5Sum checksums of incoming streams. This leads to incompatibility with LogScale's client. MinIO provides a workaround: use the `--compat` option instead to start the server. For example:

shell

    $ ./minio --compat server /data

#### Enter search term