We ran into this issue as well. If you set the environment variable to anything random, it'll get ignored and control will pass through to .aws/credentials
We used "n/a" It's kind of annoying that the s3 connection is a) required, and b) poorly supported as an env var. On Tue, May 24, 2016 at 8:37 AM Tyrone Hinderson <[email protected]> wrote: > I was logging to S3 in 1.7.0, but now I need to create an S3 "Connection" > in airflow (for remote_log_conn_id) to keep doing that in 1.7.1.2. Rather > than set this "S3" connection in the UI, I'd like set a AIRFLOW_CONN_S3 env > variable. What does an airlfow-friendly s3 "connection string" look like? >
