You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2018/03/05 23:40:00 UTC

[jira] [Resolved] (AIRFLOW-236) Support passing S3 credentials through environmental variables

     [ https://issues.apache.org/jira/browse/AIRFLOW-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ash Berlin-Taylor resolved AIRFLOW-236.
---------------------------------------
    Resolution: Fixed

This is possible, both using the AWS standard {{AWS_ACCESS_KEY_ID}} and via specifying connections via env vars with {{AIRFLOW_CONN_S3=s3://....}}

> Support passing S3 credentials through environmental variables
> --------------------------------------------------------------
>
>                 Key: AIRFLOW-236
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-236
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jakob Homan
>            Priority: Major
>
> Right now we expect S3 configs to be passed through one of a variety of config files, or through extra parameters in the connection screen.  It'd be nice to be able to pass these through env variables and note as such through the extra parameters.  This would lessen the need to include credentials in the webapp itself.
> Alternatively, for logging (rather than as a connector), it might just be better for Airflow to use the profie defined as AWS_DEFAULT and avoid needed an explicit configuration at all.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)