We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In a professional environment, it is common to have access to an "on premise" back-end with S3 API (e.g. see https://geekflare.com/self-hosted-s3/).
The s3-bash4 tool only allows to access AWS instance, thus is not usable in such private infrastructure.
s3-bash4
Could you add a way to specify the S3 domain instead of amazonaws.com so that the script can be used in a private context?
TIA
The text was updated successfully, but these errors were encountered:
To @cvle : This issue could be closed if PR #8 is merged
Sorry, something went wrong.
+1 @cvle
No branches or pull requests
In a professional environment, it is common to have access to an "on premise" back-end with S3 API (e.g. see https://geekflare.com/self-hosted-s3/).
The
s3-bash4tool only allows to access AWS instance, thus is not usable in such private infrastructure.Could you add a way to specify the S3 domain instead of amazonaws.com so that the script can be used in a private context?
TIA
The text was updated successfully, but these errors were encountered: