Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support minio for mongo #164

Closed
olexiyb opened this issue Apr 7, 2024 · 3 comments
Closed

support minio for mongo #164

olexiyb opened this issue Apr 7, 2024 · 3 comments

Comments

@olexiyb
Copy link

olexiyb commented Apr 7, 2024

I see only Amazon S3 at this moment, is it possible to add support of minio

@dbazhenov
Copy link

Hi, @olexiyb

Thank you for creating the Issue

Just wanted to say that there is a discussion on the forum on a related topic, maybe someone could use it.
https://forums.percona.com/t/backup-to-non-aws-s3/29159/6

@recharte
Copy link
Collaborator

recharte commented Apr 8, 2024

Everest supports any S3-compatible API as long as it meets 2 requirements:

  1. If you use HTTPS, the TLS certificate must be signed by a trusted authority (self-signed certificates are not allowed)
  2. Your S3-compatible API must support Virtual-hosted–style requests (instances using path-style URL access will not work)

We are planning to remove both limitations in the near future:

  1. Allowing to skip TLS certificate checks is already being developed and will be part of 0.10.0 which is planned to be released at the end of April
  2. Supporting path-style URL access is in our roadmap, no ETA on this one yet.

@recharte
Copy link
Collaborator

recharte commented Jul 4, 2024

Closing this issue because because both aforementioned limitations have been addressed in v0.10.0 and minio is now supported.

@recharte recharte closed this as completed Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants