RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-lifecycle-hooks.html below:

Lifecycle hooks for Amazon ECS service deployments

When a deployment starts, it goes through lifecycle stages. These stages can be in states such as IN_PROGRESS or successful. You can use lifecycle hooks, which are Lambda functions that Amazon ECS runs on your behalf at specified lifecycle stages. The functions can be either of the following:

An asynchronous API which validates the health check within 15 minutes.
A poll API which initiates another asynchronous process which evaluates the lifecycle hook completion.

After the function has finished running, it must return a hookStatus for the deployment to continue. If a hookStatus is not returned, or if the function fails, the deployment rolls back. The following are the hookStatus values:

SUCCEEDED - the deployment continues to the next lifecycle stage
FAILED â the deployment rolls back to the last successful deployment.
IN_PROGRESS â Amazon ECS runs the function again after a short period of time. By default this is a 30 second interval, however this value is customizable by returning a callBackDelay alongside the hookStatus.

The following example shows how to return a hookStatus with a custom callback delay. In this example, Amazon ECS would retry this hook in 60 seconds instead of the default 30 seconds:


{
    "hookStatus": "IN_PROGRESS",
    "callBackDelay": 60
}

When a roll back happens, Amazon ECS runs the lifecycle hooks for the following lifecycle stages:

PRODUCTION_TRAFFIC_SHIFT
TEST_TRAFFIC_SHIFT

Lifecycle payloads

When you configure lifecycle hooks for your ECS service deployments, Amazon ECS invokes these hooks at specific stages of the deployment process. Each lifecycle stage provides a JSON payload with information about the current state of the deployment. This document describes the payload structure for each lifecycle stage.

Common payload structure

All lifecycle stage payloads include the following common fields:

serviceArn - The Amazon Resource Name (ARN) of the service.
targetServiceRevisionArn - The ARN of the target service revision being deployed.
testTrafficWeights - A map of service revision ARNs to their corresponding test traffic weight percentages.
productionTrafficWeights - A map of service revision ARNs to their corresponding production traffic weight percentages.

Lifecycle stage payloads RECONCILE_SERVICE

This stage occurs at the beginning of the deployment process when the service is being reconciled. The following shows an example payload for this lifecycle stage.


{
  "serviceArn": "arn:aws:ecs:us-west-2:1234567890:service/myCluster/myService",
  "targetServiceRevisionArn": "arn:aws:ecs:us-west-2:1234567890:service-revision/myCluster/myService/01275892",
  "testTrafficWeights": {
    "arn:aws:ecs:us-west-2:1234567890:service-revision/myCluster/myService/01275892": 100,
    "arn:aws:ecs:us-west-2:1234567890:service-revision/myCluster/myService/78652123": 0
  },
  "productionTrafficWeights": {
    "arn:aws:ecs:us-west-2:1234567890:service-revision/myCluster/myService/01275892": 100,
    "arn:aws:ecs:us-west-2:1234567890:service-revision/myCluster/myService/78652123": 0
  }
}