Bug in v2.6.3: deploy waiting minutes after aws deploy finished

[vitalykarasik]

My workflow

 uses: aws-actions/amazon-ecs-deploy-task-definition@v2
        with:
          task-definition: ${{ steps.task-def.outputs.task-definition }}
          service: ${{ env.ECS_SERVICE }}
          cluster: ${{ env.ECS_CLUSTER }}
          wait-for-service-stability: true

After upgrading to v2.6.3, I often see that this step remains unfinished for a long time after the AWS ECS deployment has completed. Downgrading to v2.6.2 fixed this behavior.

[stephaneseng]

I think this is due to a change in the default values for the "exponential backoff for waiting for service stability" in @aws-sdk/client-ecs, which is now up to 600s in v2.6.3 instead of 120s in v2.6.2.

In this case, setting wait-max-delay-seconds to 15s for example fixes that (to limit this exponential backoff).

Cause

It looks like this change in these default values happened in @aws-sdk/client-ecs in its v3.995.0 release (released on 2026-02-20):

• Commit: aws/aws-sdk-js-v3@20258a5#diff-ea20e54b887a05b2172713685b5d0ec12e92391e8b1a48f1b3b1da314d036783
• v3.995.0 release: https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.995.0

But this change has just landed in amazon-ecs-deploy-task-definition v2.6.3 (released on 2026-07-01) where @aws-sdk/client-ecs has been upgraded from v3.921.0 (released on 2025-10-30) to v3.1076.0 (released on 2026-06-29):

• Commit: cc7d054
• v2.6.3 release: https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.995.0

(Note: The increase from 120s -> 600s only impacts waitUntilTasksStopped and waitUntilServicesStable from @aws-sdk/client-codedeploy.
waitUntilDeploymentSuccessful from @aws-sdk/client-codedeploy is not impacted (looks like 120s is just the default value on waiters)).

Resolution propositions

• Should the description of wait-max-delay-seconds be updated in action.yml to indicate that this exponential backoff is now up to 600s by default?
  Or maybe should this precision be removed from the description?

• Or maybe should a default value for wait-max-delay-seconds be defined?