startTimeout property
Time duration (in seconds) to wait before giving up on resolving
dependencies for a container. For example, you specify two containers in a
task definition with containerA having a dependency on containerB reaching a
COMPLETE, SUCCESS, or HEALTHY status.
If a startTimeout value is specified for containerB and it does
not reach the desired status within that time then containerA will give up
and not start. This results in the task transitioning to a
STOPPED state.
For tasks using the Fargate launch type, this parameter requires that the
task or service uses platform version 1.3.0 or later.
For tasks using the EC2 launch type, your container instances require at
least version 1.26.0 of the container agent to enable a
container start timeout value. However, we recommend using the latest
container agent version. For information about checking your agent version
and updating to the latest version, see Updating
the Amazon ECS Container Agent in the Amazon Elastic Container
Service Developer Guide. If you are using an Amazon ECS-optimized Linux
AMI, your instance needs at least version 1.26.0-1 of the
ecs-init package. If your container instances are launched from
version 20190301 or later, then they contain the required
versions of the container agent and ecs-init. For more
information, see Amazon
ECS-optimized Linux AMI in the Amazon Elastic Container Service
Developer Guide.
Implementation
final int? startTimeout;