Stephen Baynham created AIRFLOW-1968:
----------------------------------------
Summary: Re-Add Assume Role Support to S3 (And probably other AWS
hooks)
Key: AIRFLOW-1968
URL: https://issues.apache.org/jira/browse/AIRFLOW-1968
Project: Apache Airflow
Issue Type: New Feature
Components: aws, boto3
Affects Versions: 1.9.0
Reporter: Stephen Baynham
Priority: Minor
In Airflow 1.8, you could add S3 connections and use S3 hooks with assumed
roles. When the AWS credential functionality was refactored for 1.9, this
capability was removed and only key/secret credentials are now allowed. This
has broken a number of dags at Twitch- it's not unusual for us to connect to
buckets from other teams or third parties with an assumed role to decouple this
capability from local IAM concerns (having a lot of third parties change the
permitted ARN can be labor intensive so we'd prefer not to ever have to do it).
Please re-add this capability, ideally in the new AWS hook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
