(ecs-patterns): Add support to define specific subnets and security groups on QueueProcessingFargateService construct

[lgvo]

Add support to define specific subnets and security groups on QueueProcessingFargateService.

Use Case

I want to be able to specific subnets and security groups for my Fargate service on QueueProcessingFargateService construct.

Example: Allow better security posture with isolated subnets and specific security groups.

Proposed Solution

  const queueProcessingService = new QueueProcessingFargateService(stack, 'queue-processing', {
        vpc,
        image: ContainerImage.fromDockerImageAsset(dockerImage),
        taskSubnets: { subnetType: ec2.SubnetType.ISOLATED },
        securityGroups: [securityGroup]
    });

Other

Current work around:

  const queueProcessingService = new QueueProcessingFargateService(stack, 'queue-processing', {
        vpc,
        image: ContainerImage.fromDockerImageAsset(dockerImage),
    });
    const cfnService = queueProcessingService.service.node.children[0] as ecs.CfnService;
    cfnService.networkConfiguration = {
        awsvpcConfiguration: {
            assignPublicIp: 'DISABLED',
            subnets: vpc.isolatedSubnets.map(s => s.subnetId),
            securityGroups: [securityGroup.securityGroupId]
        }
    };

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

---

This is a 🚀 Feature Request

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