Skip to content

Does --wait-until=deployed option require more action policies than --wait-until=stable? #850

Description

@tomoya

ecspresso version: v2.5.0

An error occurred when using the --wait-until=deployed option.

2025-06-13T15:38:46.864+09:00 [ERROR] FAILED. failed to list service deployments: operation error ECS: ListServiceDeployments, https response error StatusCode: 400, RequestID: REQUESTID, AccessDeniedException: User: arn:aws:iam::ACCOUNTID:user/USERNAME is not authorized to perform: ecs:ListServiceDeployments on resource: arn:aws:ecs:ap-northeast-1:ACCOUNTID:service/CLUSTERNAME/SERVICENAME because no identity-
based policy allows the ecs:ListServiceDeployments action

However, ecspresso verify completed successfully.

After that, I tried removing --wait-until=deployed and the deployment was successful.

I haven't tried it yet, but if you add ecs:ListServiceDeployments to my policy, the deployment would be successful.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions