aws-ecs-patterns (QueueProcessingFargateService): Make Target CPU Utilization configurable

[VarshaVid]

Describe the feature

The current scaling policy defined in QueueProcessingServiceBase sets the targetUtilizationPercent at 50%, and is not configurable.

aws-cdk/packages/@aws-cdk/aws-ecs-patterns/lib/base/queue-processing-service-base.ts

Line 344 in fd5808f

protected configureAutoscalingForService(service: BaseService) {

This value should be configurable by users.

Use Case

We have an application that works on a high throughput queue, but the processing is not latency-sensitive and we can afford to run hotter on the CPU, allowing us to run fewer ECS tasks and save on cost.

Proposed Solution

This value should be configurable through an optional parameter added to QueueProcessingServiceBaseProps (and , by extension, QueueProcessingFargateServiceProps). If not specified by the user, this will default to 50% utilization, for backward compatibility.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

1.141

Environment details (OS name and version, etc.)

NodeJS-14

[peterwoodworth]

Our L3 constructs will make some opinionated choices like this, this is something we could add but typically if you need fine-grained control then building patterns with your own L2 constructs is a better choice if the modifications you need to make aren't easily achievable with escape hatches

[AnuragMohapatra]

This issue should be closed after the merge of PR #28315 which introduces a prop to change the target CPU utilization on the main construct instead of base props.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.