DeploymentLifecycleHook
A deployment lifecycle hook runs custom logic or pauses the deployment at specific stages of the deployment process. You can use Lambda functions or pause hooks as hook targets.
For more information, see Lifecycle hooks for Amazon ECS service deployments in the Amazon Elastic Container Service Developer Guide.
Contents
- hookDetails
-
Use this field to specify custom parameters that Amazon ECS passes to your Lambda function on each invocation. This field is not used for
PAUSEhooks.Type: JSON value
Required: No
- hookTargetArn
-
The Amazon Resource Name (ARN) of the hook target. For
AWS_LAMBDAhooks, this is the Lambda function ARN. This field is not applicable forPAUSEhooks.You must provide this parameter when configuring an
AWS_LAMBDAlifecycle hook.Type: String
Required: No
- lifecycleStages
-
The lifecycle stages at which to run the hook. Choose from these valid values:
-
RECONCILE_SERVICE
The reconciliation stage that only happens when you start a new service deployment with more than 1 service revision in an ACTIVE state.
You can use a lifecycle hook for this stage.
-
PRE_SCALE_UP
The green service revision has not started. The blue service revision is handling 100% of the production traffic. There is no test traffic.
You can use a lifecycle hook for this stage.
-
POST_SCALE_UP
The green service revision has started. The blue service revision is handling 100% of the production traffic. There is no test traffic.
You can use a lifecycle hook for this stage.
-
TEST_TRAFFIC_SHIFT
The blue and green service revisions are running. The blue service revision handles 100% of the production traffic. The green service revision is migrating from 0% to 100% of test traffic.
You can use a lifecycle hook for this stage.
-
POST_TEST_TRAFFIC_SHIFT
The test traffic shift is complete. The green service revision handles 100% of the test traffic.
You can use a lifecycle hook for this stage.
-
PRE_PRODUCTION_TRAFFIC_SHIFT
Occurs before production traffic shift. For linear and canary deployments, this stage is invoked before every traffic shift step.
You can use a lifecycle hook for this stage.
-
PRODUCTION_TRAFFIC_SHIFT
Production traffic is shifting to the green service revision. The green service revision is migrating from 0% to 100% of production traffic. For linear and canary deployments, this stage is invoked at every traffic shift step.
You can use a lifecycle hook for this stage.
-
POST_PRODUCTION_TRAFFIC_SHIFT
The production traffic shift is complete.
You can use a lifecycle hook for this stage.
Note
PAUSEhooks cannot be configured atTEST_TRAFFIC_SHIFTorPRODUCTION_TRAFFIC_SHIFTstages. These stages are only valid forAWS_LAMBDAhooks.You must provide this parameter when configuring a deployment lifecycle hook.
Type: Array of strings
Valid Values:
RECONCILE_SERVICE | PRE_SCALE_UP | POST_SCALE_UP | TEST_TRAFFIC_SHIFT | POST_TEST_TRAFFIC_SHIFT | PRE_PRODUCTION_TRAFFIC_SHIFT | PRODUCTION_TRAFFIC_SHIFT | POST_PRODUCTION_TRAFFIC_SHIFTRequired: No
-
- roleArn
-
The Amazon Resource Name (ARN) of the IAM role that grants Amazon ECS permission to call Lambda functions on your behalf.
For more information, see Permissions required for Lambda functions in Amazon ECS blue/green deployments in the Amazon Elastic Container Service Developer Guide.
Type: String
Required: No
- targetType
-
The type of action the lifecycle hook performs. Valid values are:
-
AWS_LAMBDA- Invokes a Lambda function at the specified lifecycle stage. This is the default value. -
PAUSE- Pauses the deployment at the specified lifecycle stage until you callContinueServiceDeploymentto continue or roll back.
This field is optional. If not specified, the default value is
AWS_LAMBDA.Type: String
Valid Values:
AWS_LAMBDA | PAUSERequired: No
-
- timeoutConfiguration
-
The timeout configuration for the lifecycle hook. This specifies how long Amazon ECS waits before taking the timeout action if the hook is not resolved.
Type: DeploymentLifecycleHookTimeoutConfiguration object
Required: No
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: