feat(ecs): add built-in Linear and Canary deployments

[mazyu36]

Issue # (if applicable)

Closes #35986
Closes #35987

Reason for this change

Add new built-in Linear and Canary deployment strategies for ECS services to enable progressive and controlled production deployments.

Ref: Amazon ECS now supports built-in Linear and Canary deployments

Description of changes

• Add CanaryConfiguration and LinearConfiguration interfaces to BaseServiceOptions
• Extend DeploymentStrategy enum with LINEAR and CANARY values

Describe any new or updated permissions being added

N/A

Description of how you validated changes

Add unit tests and integ tests.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[kg-aws]

Thank you for the contribution. I have added my opinion to how we can implement this features in CDK L2 construct.

[kg-aws]

Given how similar these two interfaces are we can combine them in to single interface as following.

/**
 * Configuration for ECS service deployments (linear and canary)
 */
export interface TrafficShiftConfig {
  /**
   * The percentage of traffic to shift
   * @minimum 0.1 for canary, 3 for linear
   * @maximum 100
   */
  readonly stepPercent: number;

  /**
   * The number of minutes to wait between each step
   * @minimum 0
   * @maximum 1440
   */
  readonly stepBakeTime: Duration;
}

[kg-aws]

Instead of setting values directly in the constructor, we can add methods that automatically configure the strategy along with the provided config. This way, existing users would only need to call these methods without modifying the constructor.

public configureLinearDeployment(config: TrafficShiftConfig): void {
    if (!this.isEcsDeploymentController) {
      throw new ValidationError('Linear configuration requires the ECS deployment controller.', this);
    }

    this.validateLinearConfiguration(config);

    // Update the deployment configuration with linear settings and set strategy to LINEAR
    const currentConfig = this.resource.deploymentConfiguration || {};
    this.resource.deploymentConfiguration = {
      ...currentConfig,
      strategy: DeploymentStrategy.LINEAR,
      linearConfiguration: {
        stepPercent: config.stepPercent,
        stepBakeTimeInMinutes: config.stepBakeTime.toMinutes(),
      },
    };
}

public configureCanaryDeployment(config: TrafficShiftConfig): void {
    if (!this.isEcsDeploymentController) {
      throw new ValidationError('Canary configuration requires the ECS deployment controller.', this);
    }

   this.validateCanaryConfiguration(config);

    // Update the deployment configuration with canary settings and set strategy to CANARY
    const currentConfig = this.resource.deploymentConfiguration || {};
    this.resource.deploymentConfiguration = {
      ...currentConfig,
      strategy: DeploymentStrategy.CANARY,
      canaryConfiguration: {
        canaryPercent: config.stepPercent,
        canaryBakeTimeInMinutes: config.stepBakeTime.toMinutes(),
      },
    };
}

[mazyu36]

Thanks. I've updated.

[badmintoncryer]

Thanks! I've added a minor comment.

[badmintoncryer]

It might be better to consider the case that stepBakeTime is set less than a minute such as 10 seconds.

I think this condition causes synth error.

aws-cdk/packages/aws-cdk-lib/core/lib/duration.ts

Line 336 in 10de047

if (!Number.isInteger(value) && integral) {

[mazyu36]

Thanks.
I've added a validation.

Pull request has been modified.

[leonmk-aws]

Thank you for your contribution !

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

✅ The pull request has been merged at e8afe59

This pull request spent 44 minutes 58 seconds in the queue, including 29 minutes 12 seconds running CI.
The checks were run in-place.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • feat(ecs): add built-in Linear and Canary deployments  #35981
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • feat(ecs): add built-in Linear and Canary deployments  #35981
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.