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
Is your feature request related to a problem? Please describe. Extend configuration settings for s3...
Describe the solution you'd like
http://s3.amazonaws.com/BUCKET/KEY
draft solution file s3.go:
// Init initializes the media handler. func (ah *awshandler) Init(jsconf string) error { //// // remove check of the set region // if ah.conf.Region == "" { // return errors.New("missing Region") // } //// if sess, err = session.NewSession(&aws.Config{ Region: aws.String(ah.conf.Region), Credentials: credentials.NewStaticCredentials(ah.conf.AccessKeyId, ah.conf.SecretAccessKey, ""), // new block ++ { DisableSSL: aws.Bool(ah.conf.disableSSL), S3ForcePathStyle: aws.Bool(ah.conf.s3ForcePathStyle), Endpoint: aws.String(ah.conf.Endpoint), // new block -- } }); err != nil { return err } ////
The text was updated successfully, but these errors were encountered:
use path-style addressing, ex. http://s3.amazonaws.com/BUCKET/KEY.
I don't understand this one.
option for disable SSL when sending requests option for setting Region
OK
Sorry, something went wrong.
use path-style addressing, ex. http://s3.amazonaws.com/BUCKET/KEY. I don't understand this one.
field S3ForcePathStyle and Endpoint in struct Config
S3ForcePathStyle
Endpoint
Config
https://github.com/aws/aws-sdk-go/blob/main/aws/config.go#L127
Ok
more s3 config options per #673
2da517f
Released. Closing.
No branches or pull requests
Is your feature request related to a problem? Please describe.
Extend configuration settings for s3...
Describe the solution you'd like
http://s3.amazonaws.com/BUCKET/KEY
.draft solution
file s3.go:
The text was updated successfully, but these errors were encountered: