Add support for "RequestPay: requester" option in Amazon S3's Operators, Sensors and Triggers

[Ferdinanddb]

Description

As a user that needs to manipulate objects inside S3 buckets where the option "RequestPayer" must be set to "requester", it would be awesome that the different S3 Operators, Sensors and Triggers support this option, either via a method argument or within the AWS connection.

Use case/motivation

I consume data within S3 from data providers and the option "RequestPayer" must be set to "requester".

The different S3 operators and sensors seem to not support this option out of the box, so I developed my own custom python functions which are executed using the PythonOperator, but I feel like this option could be useful in general so I decided to create this issue.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[valentinDruzhinin]

@potiuk could you please assign this issue? I would like to implement this feature.

[vijay-x-Raj]

I would like to work on this issue can you assign it to me?

[gopidesupavan]

@valentinDruzhinin assigned to you, as you requested first. if your not working please post it will assign this to @codeName-Vijayraj

[valentinDruzhinin]

@valentinDruzhinin assigned to you, as you requested first. if your not working please post it will assign this to @codeName-Vijayraj

Thanks, I'll work on this issue