Builder

Information about the CloudWatch alarms.

The time period when both blue and green service revisions are running simultaneously after the production traffic has shifted.

The deployment circuit breaker can only be used for services using the rolling update (ECS) deployment type.

An array of deployment lifecycle hook objects to run custom logic at specific stages of the deployment lifecycle.

If a service is using the rolling update (ECS) deployment type, the maximumPercent parameter represents an upper limit on the number of your service's tasks that are allowed in the RUNNING or PENDING state during a deployment, as a percentage of the desiredCount (rounded down to the nearest integer). This parameter enables you to define the deployment batch size. For example, if your service is using the REPLICA service scheduler and has a desiredCount of four tasks and a maximumPercent value of 200%, the scheduler may start four new tasks before stopping the four older tasks (provided that the cluster resources required to do this are available). The default maximumPercent value for a service using the REPLICA service scheduler is 200%.

If a service is using the rolling update (ECS) deployment type, the minimumHealthyPercent represents a lower limit on the number of your service's tasks that must remain in the RUNNING state during a deployment, as a percentage of the desiredCount (rounded up to the nearest integer). This parameter enables you to deploy without using additional cluster capacity. For example, if your service has a desiredCount of four tasks and a minimumHealthyPercent of 50%, the service scheduler may stop two existing tasks to free up cluster capacity before starting two new tasks.

The deployment strategy for the service. Choose from these valid values:

construct an aws.sdk.kotlin.services.ecs.model.DeploymentAlarms inside the given block

construct an aws.sdk.kotlin.services.ecs.model.DeploymentCircuitBreaker inside the given block