{"action":"opened","issue":{"url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/247","labels_url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/247/labels{/name}","comments_url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/247/comments","events_url":"https://api.github.com/repos/aws/amazon-ecs-agent/issues/247/events","html_url":"https://github.com/aws/amazon-ecs-agent/issues/247","id":115019892,"number":247,"title":"env-file support","user":{"login":"tbinna","id":1586709,"avatar_url":"https://avatars.githubusercontent.com/u/1586709?v=3","gravatar_id":"","url":"https://api.github.com/users/tbinna","html_url":"https://github.com/tbinna","followers_url":"https://api.github.com/users/tbinna/followers","following_url":"https://api.github.com/users/tbinna/following{/other_user}","gists_url":"https://api.github.com/users/tbinna/gists{/gist_id}","starred_url":"https://api.github.com/users/tbinna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tbinna/subscriptions","organizations_url":"https://api.github.com/users/tbinna/orgs","repos_url":"https://api.github.com/users/tbinna/repos","events_url":"https://api.github.com/users/tbinna/events{/privacy}","received_events_url":"https://api.github.com/users/tbinna/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-04T10:20:18Z","updated_at":"2015-11-04T10:20:18Z","closed_at":null,"body":"I open this issue to pick up a point that was made in #127 to support the `--env-file` parameter. As pointed out in #127 this would be useful e.g. to add some environment variables that contain sensitive information. This way sensitive environment variables could be stored in a private S3 bucket and be pulled in from there either directly or via a mounted volume.\r\n\r\nIf the `--env-file` parameter is supported I guess the documentation on [Task Definition Parameters](http://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#container_definition_environment) could also be improved. Under `environment` it is mentioned that it is not recommended to put sensitive information in there, however it does not point to a solution on how to do this otherwise.\r\n\r\nExtract from issue #127:\r\n\r\n[...] Ideally it would allow an s3 endpoint:\r\n```\r\n\"containerDefinitions\":[\r\n  {\r\n    \"env_file\":[\r\n      { \"bucket\":\"my-bucket\", \"key\":\"myenvlist\" }\r\n    ]\r\n  }\r\n]\r\n```\r\nElastic Beanstalk lets you do something similar in the Dockerrun.aws.json for docker private repository configuration:\r\n```\r\n\"Authentication\":{\r\n  \"Bucket\":\"my-bucket\",\r\n  \"Key\":\"mydockercfg\"\r\n},\r\n```"}}