public void setStartTimeout(Integer startTimeout) {
        this.startTimeout = startTimeout;
    }
<p>
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
<code>COMPLETE</code>, <code>SUCCESS</code>, or <code>HEALTHY</code> status. If a <code>startTimeout</code> value
is specified for containerB and it doesn't reach the desired status within that time then containerA gives up and
not start. This results in the task transitioning to a <code>STOPPED</code> state.
</p>
<note>
<p>
When the <code>ECS_CONTAINER_START_TIMEOUT</code> container agent configuration variable is used, it's enforced
independently from this start timeout value.
</p>
</note>
<p>
For tasks using the Fargate launch type, the task or service requires the following platforms:
</p>
<ul>
<li>
<p>
Linux platform version <code>1.3.0</code> or later.
</p>
</li>
<li>
<p>
Windows platform version <code>1.0.0</code> or later.
</p>
</li>
</ul>
<p>
For tasks using the EC2 launch type, your container instances require at least version <code>1.26.0</code> of the
container agent to use 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 <a
href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html">Updating the Amazon ECS
Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you're using an Amazon
ECS-optimized Linux AMI, your instance needs at least version <code>1.26.0-1</code> of the <code>ecs-init</code>
package. If your container instances are launched from version <code>20190301</code> or later, then they contain
the required versions of the container agent and <code>ecs-init</code>. For more information, see <a
href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html">Amazon ECS-optimized
Linux AMI</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.
</p>
<p>
The valid values are 2-120 seconds.
</p>

@param startTimeout
       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 <code>COMPLETE</code>, <code>SUCCESS</code>, or <code>HEALTHY</code> status. If a
       <code>startTimeout</code> value is specified for containerB and it doesn't reach the desired status within
       that time then containerA gives up and not start. This results in the task transitioning to a
       <code>STOPPED</code> state.</p> <note>
       <p>
       When the <code>ECS_CONTAINER_START_TIMEOUT</code> container agent configuration variable is used, it's
       enforced independently from this start timeout value.
       </p>
       </note>
       <p>
       For tasks using the Fargate launch type, the task or service requires the following platforms:
       </p>
       <ul>
       <li>
       <p>
       Linux platform version <code>1.3.0</code> or later.
       </p>
       </li>
       <li>
       <p>
       Windows platform version <code>1.0.0</code> or later.
       </p>
       </li>
       </ul>
       <p>
       For tasks using the EC2 launch type, your container instances require at least version <code>1.26.0</code>
       of the container agent to use 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 <a
       href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-update.html">Updating the
       Amazon ECS Container Agent</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. If you're
       using an Amazon ECS-optimized Linux AMI, your instance needs at least version <code>1.26.0-1</code> of the
       <code>ecs-init</code> package. If your container instances are launched from version <code>20190301</code>
       or later, then they contain the required versions of the container agent and <code>ecs-init</code>. For
       more information, see <a
       href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html">Amazon
       ECS-optimized Linux AMI</a> in the <i>Amazon Elastic Container Service Developer Guide</i>.
       </p>
       <p>
       The valid values are 2-120 seconds.
aws-java-sdk-ecs/src/main/java/com/amazonaws/services/ecs/model/ContainerDefinition.java