You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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: