Skip to content

Commit d7a58e2

Browse files
author
awstools
committed
docs(client-ecs): Updating stop-task API to encapsulate containers with custom stop signal
1 parent b9bad19 commit d7a58e2

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

clients/client-ecs/src/commands/StopTaskCommand.ts

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,10 +30,12 @@ export interface StopTaskCommandOutput extends StopTaskResponse, __MetadataBeare
3030
* <p>Stops a running task. Any tags associated with the task will be deleted.</p>
3131
* <p>When you call <code>StopTask</code> on a task, the equivalent of <code>docker
3232
* stop</code> is issued to the containers running in the task. This results in a
33-
* <code>SIGTERM</code> value and a default 30-second timeout, after which the
34-
* <code>SIGKILL</code> value is sent and the containers are forcibly stopped. If the
35-
* container handles the <code>SIGTERM</code> value gracefully and exits within 30 seconds
36-
* from receiving it, no <code>SIGKILL</code> value is sent.</p>
33+
* stop signal value and a default 30-second timeout, after which the
34+
* <code>SIGKILL</code> value is sent and the containers are forcibly stopped. This
35+
* signal can be defined in your container image with the <code>STOPSIGNAL</code> instruction
36+
* and will default to <code>SIGTERM</code>. If the container handles the <code>SIGTERM</code>
37+
* value gracefully and exits within 30 seconds from receiving it, no <code>SIGKILL</code> value
38+
* is sent.</p>
3739
* <p>For Windows containers, POSIX signals do not work and runtime stops the container by
3840
* sending a <code>CTRL_SHUTDOWN_EVENT</code>. For more information, see <a href="https://github.com/moby/moby/issues/25982">Unable to react to graceful shutdown
3941
* of (Windows) container #25982</a> on GitHub.</p>

codegen/sdk-codegen/aws-models/ecs.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15356,7 +15356,7 @@
1535615356
}
1535715357
],
1535815358
"traits": {
15359-
"smithy.api#documentation": "<p>Stops a running task. Any tags associated with the task will be deleted.</p>\n <p>When you call <code>StopTask</code> on a task, the equivalent of <code>docker\n\t\t\t\tstop</code> is issued to the containers running in the task. This results in a\n\t\t\t\t<code>SIGTERM</code> value and a default 30-second timeout, after which the\n\t\t\t\t<code>SIGKILL</code> value is sent and the containers are forcibly stopped. If the\n\t\t\tcontainer handles the <code>SIGTERM</code> value gracefully and exits within 30 seconds\n\t\t\tfrom receiving it, no <code>SIGKILL</code> value is sent.</p>\n <p>For Windows containers, POSIX signals do not work and runtime stops the container by\n\t\t\tsending a <code>CTRL_SHUTDOWN_EVENT</code>. For more information, see <a href=\"https://github.com/moby/moby/issues/25982\">Unable to react to graceful shutdown\n\t\t\t\tof (Windows) container #25982</a> on GitHub.</p>\n <note>\n <p>The default 30-second timeout can be configured on the Amazon ECS container agent\n\t\t\t\twith the <code>ECS_CONTAINER_STOP_TIMEOUT</code> variable. For more information, see\n\t\t\t\t\t<a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html\">Amazon ECS Container Agent Configuration</a> in the\n\t\t\t\t\t<i>Amazon Elastic Container Service Developer Guide</i>.</p>\n </note>",
15359+
"smithy.api#documentation": "<p>Stops a running task. Any tags associated with the task will be deleted.</p>\n <p>When you call <code>StopTask</code> on a task, the equivalent of <code>docker\n\t\t\t\tstop</code> is issued to the containers running in the task. This results in a\n\t\t\t\tstop signal value and a default 30-second timeout, after which the\n\t\t\t\t<code>SIGKILL</code> value is sent and the containers are forcibly stopped. This \n\t\t\t\tsignal can be defined in your container image with the <code>STOPSIGNAL</code> instruction\n\t\t\t\tand will default to <code>SIGTERM</code>. If the container handles the <code>SIGTERM</code>\n\t\t\t\tvalue gracefully and exits within 30 seconds from receiving it, no <code>SIGKILL</code> value\n\t\t\t\tis sent.</p>\n <p>For Windows containers, POSIX signals do not work and runtime stops the container by\n\t\t\tsending a <code>CTRL_SHUTDOWN_EVENT</code>. For more information, see <a href=\"https://github.com/moby/moby/issues/25982\">Unable to react to graceful shutdown\n\t\t\t\tof (Windows) container #25982</a> on GitHub.</p>\n <note>\n <p>The default 30-second timeout can be configured on the Amazon ECS container agent\n\t\t\t\twith the <code>ECS_CONTAINER_STOP_TIMEOUT</code> variable. For more information, see\n\t\t\t\t\t<a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html\">Amazon ECS Container Agent Configuration</a> in the\n\t\t\t\t\t<i>Amazon Elastic Container Service Developer Guide</i>.</p>\n </note>",
1536015360
"smithy.api#examples": [
1536115361
{
1536215362
"title": "To stop a task",

0 commit comments

Comments
 (0)