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.

Sign up for GitHub

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

Jump to bottom

feat: discourage use of DesiredCount for auto-scaled ECS services #1652

Open
2 tasks
otterley opened this issue Apr 4, 2024 · 1 comment
Open
2 tasks

feat: discourage use of DesiredCount for auto-scaled ECS services #1652

otterley opened this issue Apr 4, 2024 · 1 comment
Labels
feature-request A feature should be added or improved.

Comments

@otterley
Copy link

otterley commented Apr 4, 2024

Description

Report a conformance issue if DesiredCount is declared for auto-scaled ECS services.

Use Case

Declaring a DesiredCount for an ECS service can lead to availability issues.

Suppose a Service's DesiredCount is set to 2, and Application Auto Scaling has increased the count to 10 to accommodate current demand. When the stack is then updated to deploy new code, the DesiredCount will be reset to 2, leading to overload and failures that may require manual recovery.

Proposed Solution

Report a failure if DesiredCount is declared for such services.

Other information

No response

Acknowledge

  • I may be able to implement this feature request
  • This feature might incur a breaking change
@otterley otterley added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Apr 4, 2024
@dontirun dontirun removed the needs-triage This issue or PR still needs to be triaged. label Apr 12, 2024
@dontirun
Copy link
Collaborator

Looks like a good rule to add to the Additional Rules

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request A feature should be added or improved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@otterley @dontirun