Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ECS] Waiter: Increase ServicesStable Waiter Time to "x" Time (30 or 60 minutes?) #2474

Open
colinbjohnson opened this issue Nov 19, 2024 · 0 comments
Assignees
Labels
Proposed Community submitted issue

Comments

@colinbjohnson
Copy link

colinbjohnson commented Nov 19, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request

I would like to propose that AWS increase the "ServicesStable" waiter time (link for botocore as of 2024-11-18: https://github.com/boto/botocore/blob/develop/botocore/data/ecs/2014-11-13/waiters-2.json#L42-L72) to some amount of time greater than 10 minutes.

Which service(s) is this request for?

ECS, ECS Fargate

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

We (and a number of AWS customers) that use the aws ecs wait services-stable command (or similar commands within SDKs) may have deployments that take > 10 minutes to become stable. There is no native way to use the waiter for a deployment that takes > 10 minutes.

Are you currently working around this issue?

I have seen a number of different ways of working around this:

  • writing our own waiter (you can see these online)
  • wrapping the AWS waiter with code so the waiter itself is called repeatedly
  • using a different method for determining if/when a deployment is complete (EventBridge?)
  • not utilizing a waiter (and assuming the deployment succeeded)
  • using a different method for deploying ECS Service updates
  • something else?

Proposed Solution(s)

Additional context

Attachments

If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Proposed Community submitted issue
Projects
None yet
Development

No branches or pull requests

2 participants