aws_autoscaling: Option to permanently suspend processes
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
An option to create/configure an ASG to have processes always suspended.
Currently processes like such as `AZRebalance` can only be suspended during a CDK deployment, there's no option to mark a process as always suspended.
### Use Case
AZRebalance interacts poorly with warm pools, during capacity shortages and with the long shutdown time of GPU instances.
Additionally our system frequently adjusts the desired capacity, having another process also mess with the running instances causes a disturbance that makes our control system back off.
So overall having this process running is just undesirable. Currently we suspend it manually after creating an ASG through the CDK, it would be nicer if the CDK could suspend it at creation time.
### Proposed Solution
_No response_
### Other Information
_No response_
### Acknowledgements
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### AWS CDK Library version (aws-cdk-lib)
2.209.1
### AWS CDK CLI version
2.1033.0
### Environment details (OS name and version, etc.)
Debian 13
Contributor guide
Research direction
Start with the aws_autoscaling ASG construct and its synthesized CloudFormation template tests. Trace the existing creation-time process configuration and determine where an always-suspended option would belong. Done means users can configure the requested process suspension when creating an ASG, with coverage for the synthesized result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100