DaemonContainerDefinition

The command that's passed to the container.

The number of cpu units reserved for the container.

The dependencies defined for container startup and shutdown. A container can contain multiple dependencies on other containers in a task definition.

The entry point that's passed to the container.

The environment variables to pass to a container.

A list of files containing the environment variables to pass to a container.

If the essential parameter of a container is marked as true, and that container fails or stops for any reason, all other containers that are part of the task are stopped.

The FireLens configuration for the container. This is used to specify and configure a log router for container logs.

The container health check command and associated configuration parameters for the container.

The image used to start the container. This string is passed directly to the Docker daemon. Images in the Docker Hub registry are available by default. Other repositories are specified with either <i>repository-url</i>/<i>image</i>:<i>tag</i> or <i>repository-url</i>/<i>image</i>@<i>digest</i> .

When this parameter is true, you can deploy containerized applications that require stdin or a tty to be allocated.

Linux-specific modifications that are applied to the container configuration, such as Linux kernel capabilities.

The log configuration specification for the container.

The amount (in MiB) of memory to present to the container. If the container attempts to exceed the memory specified here, the container is killed.

The soft limit (in MiB) of memory to reserve for the container.

The mount points for data volumes in your container.

The name of the container. Up to 255 letters (uppercase and lowercase), numbers, underscores, and hyphens are allowed.

When this parameter is true, the container is given elevated privileges on the host container instance (similar to the root user).

When this parameter is true, a TTY is allocated.

When this parameter is true, the container is given read-only access to its root file system.

The private repository authentication credentials to use.

The restart policy for the container. When you set up a restart policy, Amazon ECS can restart the container without needing to replace the task.

The secrets to pass to the container.

Time duration (in seconds) to wait before giving up on resolving dependencies for a container.

Time duration (in seconds) to wait before the container is forcefully killed if it doesn't exit normally on its own.

A list of namespaced kernel parameters to set in the container.

A list of ulimits to set in the container.

The user to use inside the container.

The working directory to run commands inside the container in.