From commits-return-11916-archive-asf-public=cust-asf.ponee.io@airflow.incubator.apache.org Sat Jan 6 03:58:11 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 00652180647 for ; Sat, 6 Jan 2018 03:58:11 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E4B5B160C27; Sat, 6 Jan 2018 02:58:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3718A160C28 for ; Sat, 6 Jan 2018 03:58:10 +0100 (CET) Received: (qmail 55154 invoked by uid 500); 6 Jan 2018 02:58:09 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 55145 invoked by uid 99); 6 Jan 2018 02:58:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Jan 2018 02:58:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id D62A7C36F0 for ; Sat, 6 Jan 2018 02:58:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id xO11G-mUB7gM for ; Sat, 6 Jan 2018 02:58:08 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 267495F3B5 for ; Sat, 6 Jan 2018 02:58:08 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 3FF88E0EFA for ; Sat, 6 Jan 2018 02:58:07 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 7488E240FA for ; Sat, 6 Jan 2018 02:58:03 +0000 (UTC) Date: Sat, 6 Jan 2018 02:58:03 +0000 (UTC) From: "Stephen Baynham (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AIRFLOW-1968) Re-Add Assume Role Support to S3 (And probably other AWS hooks) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRFLOW-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314323#comment-16314323 ] Stephen Baynham commented on AIRFLOW-1968: ------------------------------------------ Submitted as: https://github.com/apache/incubator-airflow/pull/2918 > 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 > Assignee: 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)