Skip to content

Is it possible to use S3 compatible providers? #100

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

Open
FANMixco opened this issue May 5, 2025 · 0 comments
Open

Is it possible to use S3 compatible providers? #100

FANMixco opened this issue May 5, 2025 · 0 comments

Comments

@FANMixco
Copy link

FANMixco commented May 5, 2025

Fellows,

I'm wondering if there is an option to use the S3 compatible providers:
https://rclone.org/s3/

Maybe there could be a free input text where you could a configuration like the one Gemini provided me:

[my-onprem-s3]
type = s3
provider = Other
access_key_id = YOUR_ACCESS_KEY
secret_access_key = YOUR_SECRET_KEY
endpoint = http://your-onprem-s3-endpoint:port
# region = (optional, if applicable)
# signature_version = v4 (or v2, depending on your provider)
# s3_force_path_style = true (if your provider requires path-style)

Key Considerations for On-Premise S3:

  • Endpoint URL: Getting the correct endpoint URL is the most important step.
  • Authentication: Ensure you have the correct access keys and secret keys configured for your on-premise S3.
  • Networking: Your machine running Rclone needs to be able to network and reach the IP address or hostname of your on-premise S3 service. Firewalls or network configurations might need adjustments.
  • Features: While most S3-compatible providers implement the core S3 API, some advanced features or specific behaviors might differ from standard AWS S3. If you encounter issues with certain Rclone commands, it could be due to these differences.

Probably, it's outside the scope, but I'm wondering if it will be possible. Thanks :)

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

1 participant