(aws-ecs-patterns): Add capacity_provider_strategies to QueueProcessingFargateService

[purvesta]

❓ General Issue

I am trying to deploy a QueueProcessingFargateService that will deploy task containers to both FARGATE and FARGATE_SPOT, however the QueueProcessingFargateService L3 construct does not include a parameter option for capacity_provider_strategies like the FargateService L2 construct that I can see.

Environment

• CDK CLI Version: 1.100.0 (build d996c6d)
• Module Version: 1.100.0
• Node.js Version: v16.0.0
• OS: OSX Catalina
• Language: Python

Other information

The task that is running in FARGATE does not need to run at full capacity all of the time, therefore the idea behind multiple capacity providers is to deploy 10 tasks that have a weight distribution across both FARGATE and FARGATE_SPOT and also scale as the queue grows in size while utilizing the cost savings of spot.

[ABevier]

As a heads up, CloudFormation doesn't support this yet, so CDK is effectively blocked. Check out aws/containers-roadmap#631 for the Cloud Formation discussion.

[peterwoodworth]

Thanks for the heads up ABevier, but this is currently supported in cloudformation. Since it is supported by an L2, it can definitely be supported by an L3.

Currently there is no way to add what you want @purvesta, so thank you for the feature request! Here's the code where the L3 creates the L2 construct:

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

Lines 137 to 152 in c832c1b

	this.service = new FargateService(this, 'QueueProcessingFargateService', {
	cluster: this.cluster,
	desiredCount: desiredCount,
	taskDefinition: this.taskDefinition,
	serviceName: props.serviceName,
	minHealthyPercent: props.minHealthyPercent,
	maxHealthyPercent: props.maxHealthyPercent,
	propagateTags: props.propagateTags,
	enableECSManagedTags: props.enableECSManagedTags,
	platformVersion: props.platformVersion,
	deploymentController: props.deploymentController,
	securityGroups: props.securityGroups,
	vpcSubnets: props.taskSubnets,
	assignPublicIp: props.assignPublicIp,
	circuitBreaker: props.circuitBreaker,
	});

There is no capacityProviderStrategies property here, so this would have to be added here with a way to allow the user to set the property.

[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.