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
Is your feature request related to a problem? Please describe.
The s3 source supports S3's bucket ownership verification to protect against reading from buckets in unexpected accounts.
The s3 sink does not have this feature.
Describe the solution you'd like
Provide the same configurations for S3 bucket ownership as are provided in the s3 source. Use those to define the ExpectedBucketOwner parameter when writing to S3.
Additionally, this check should occur based on either of those fields being set. If they are not set, then there is no check. This is the current default and this will not break anything. As a result, I don't see any need to have a disable flag.
Additional context
Issue to add these configurations to the s3 source: #2012.
Original PR adding the check to the s3 source: #1526
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The
s3
source supports S3's bucket ownership verification to protect against reading from buckets in unexpected accounts.The
s3
sink does not have this feature.Describe the solution you'd like
Provide the same configurations for S3 bucket ownership as are provided in the
s3
source. Use those to define theExpectedBucketOwner
parameter when writing to S3.Conceptual
PutObjectRequest
:Additionally, this check should occur based on either of those fields being set. If they are not set, then there is no check. This is the current default and this will not break anything. As a result, I don't see any need to have a disable flag.
Additional context
Issue to add these configurations to the
s3
source: #2012.Original PR adding the check to the s3 source: #1526
The text was updated successfully, but these errors were encountered: