option for LoadBalancedFargateService with NLB to specify different listener port

[pahud]

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?
  If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce

The LoadBalancedFargateService class has no option to specify different ELB listerner port other than 80

aws-cdk/packages/@aws-cdk/aws-ecs-patterns/lib/fargate/load-balanced-fargate-service.ts

Line 50 in 77671ad

export class LoadBalancedFargateService extends LoadBalancedServiceBase {

And we need to addPropertyOverride() like this:

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

Provide a loadBalancerListenerPort property in LoadBalancedFargateServiceProps

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

Fargate service running as TCP service behind NLB could have listener other than 80 on the NLB. For example, NLB:8888 to containerPort:8888 on Fargate.

• Please tell us about your environment:

  • CDK CLI Version: 1.4.0 (build 175471f)
  • Module Version: 1.4.0
  • OS: OSX Mojave
  • Language: TypeScript

• 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]

This should be addressed in #4213, please let us know if this works for you! @pahud