-
Notifications
You must be signed in to change notification settings - Fork 109
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
Cross account support #45
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would be great to have a bit more support for when the S3 resource is in a different account. As it stands, if we were to put the object to another account's S3 bucket, we need to grant the bucket owner access to it.
We could extend the ExtendedClientConfiguration class to provide configuration for canned acl like this barnettj@0ca7b16.
Or we could even just make the putObject function protected and will give the consumers flexibility to extend and override the putObject method and apply whatever configuration they want to the request barnettj@3b25975.
The text was updated successfully, but these errors were encountered: