-
Notifications
You must be signed in to change notification settings - Fork 24
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
using cassandra backup with a custom s3 endpoint #14
Comments
It doesn't seem to be the case even if there is a key called endpoint in the secrets that can be set
I can interact with that endpoint from a pod:
However when trying to backup I get an error saying |
hi @puneetloya and @cscetbon yes, we do support endpoints Based on what you are using this from, configuration is either fetched from Kubernetes config map or from environment variable: The error you got has nothing to do with this backup tool, see this:
This seems like your container is not able to resolve IP of I would triple check that you can e.g. Your hostname has suffix These people are getting same error like you: aws/aws-sdk-java#1273 |
I was able to reproduce the error. It comes from the fact that aws-sdk-java uses virtual hosts instead of path-style requests when querying s3 and minio (what I use on my cluster for s3) is not configured to support it by default. I can confirm that if I use path-style requests it works as expected. I also found that AWS S3 will no longer support path style requests after September 2020 https://forums.aws.amazon.com/ann.jspa?annID=6776 so better that I make the change on my end. thanks @smiklosovic |
Does the cassandra backup support custom s3 endpoints?
For custom s3 providers like minio, will the AWS module for cassandra-backup work? it helps in validating backups in house without needing to use AWS s3.
The text was updated successfully, but these errors were encountered: