Aws Ecs Container Environment Variables

Welcome to part 3 of this blog post series on how to use amazon efs with amazon ecs and aws fargate.

Aws ecs container environment variables.

Aws supports data injection only for the following. Isn t it same functionality as docker env file. The linux host path assumes that the default data directory mount path var lib ecs data is used when the agent is started if you are not using an amazon ecs optimized ami or the ecs init package to start and maintain the container agent be sure to set the ecs host data dir agent configuration variable to the host path where the container agent s state file is located. Then you can expose your sensitive information as environment variables or in the log configuration of a container.

If your container instance was launched with a linux variant of the amazon ecs optimized ami you can set these environment variables in the etc ecs ecs config file and then restart the agent. The amazon ecs container agent running on a container instance must register with the ecs selinux capable true or ecs apparmor capable true environment variables before containers placed on that instance can use these security options. My understanding is this option essentially sets container variables. So you can use describe task definition to see the extra variables.

This is a comment and will be ignored variable value environment production. If there are environment variables specified using the environment parameter in a container definition they take precedence over the variables contained within an environment file. You can also write these configuration variables to your container instances with amazon ec2 user data at launch time. For tasks using the ec2 launch type the amazon ecs container agent running on a container instance must register the logging drivers available on that instance with the ecs available logging drivers environment variable before containers placed on that instance can use these log configuration options.

Environment variables are defined inside the container and some are passed in the task definition. If so don t we have the security issue like docker command can display this info etc. This blog provides the background about the need for this integration its scope and provides a high level view of the use cases. If multiple environment files are specified that contain the same variable they are processed from the top down.

To get the default environment of the container image you can register task definition for task with command env and the specific container image for which you want to find out and then run task this task. Can someone please share their experience. I see ecs has environment variables option to get data from aws parameter store.