Add security group parameters to ecs_patterns.LoadBalancedFargateService

[tmpm697]

Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.

• I'm submitting a ...

  • 🪲 bug report
  • 🚀 feature request
  • 📚 construct library gap
  • ☎️ security issue or vulnerability => Please see policy
  • ❓ support request => Please see note at the top of this template.

• What is the current behavior?
  Default ecs_patterns.LoadBalancedFargateService will create IAM roles and SGs but only IAM can be able to choose from its parameters, please add SGs parameters to LoadBalancedFargateService

• What is the expected behavior (or behavior of feature suggested)?

• What is the motivation / use case for changing the behavior or adding this feature?

• Please tell us about your environment:

  • CDK CLI Version: 0.39.0 (build c3a3c88)
  • Module Version: xx.xx.xx
  • OS: Archlinux
  • Language: Python

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)

[SoManyHs]

Related: #3985, #2540

[vjain16]

seems like this still a problem and no fix yet .

[MrArnoldPalmer]

@vjain16 @tmpm697 I assume you mean specifying the security groups on the load balancer, or do you mean specifying SGs on the FargateService?

If its on the load-balancer, both NetworkLoadBalancedFargateService and ApplicationLoadBalancedFargateService allow passing your own load balancer construct as a prop.

On the service itself, you can access the connections object to add new security groups.

const fargateService = new ApplicationLoadBalancedFargateService(...);

fargateService.service.connections.addSecurityGroup(someSecurityGroup);

Connections Docs