Does ApplicationLoadBalancedFargateService support task definitions with multiple containers/ports?

[lbjay]

❓ General Issue

The Question

I'm trying to create a fargate service which has an app container on port 8080 and an nginx reverse proxy container on port 443. The resulting load balancer target registration always ends up using port 8080 instead of what I want, port 443.

Environment

• CDK CLI Version: 1.19.0 (build 5597bbe)
• Module Version: aws-ecs-patterns v1.19.0
• Language: TypeScript

Other information

Example of how i'm creating the service:

    const taskDefinition = new FargateTaskDefinition(this, 'TaskDefinition');

    const appContainer = new ContainerDefinition(this, 'AppContainer', {
      image: ContainerImage.fromRegistry(APP_IMAGE),
      taskDefinition,
    });
    appContainer.addPortMappings({
      hostPort: 8080,
      containerPort: 8080
    });
    const proxyContainer = new ContainerDefinition(this, 'ProxyContainer', {
      image: ContainerImage.fromRegistry(PROXY_IMAGE),
      taskDefinition,
    })
    proxyContainer.addPortMappings({
      hostPort: 443,
      containerPort: 443,
    });

    const certificate = Certificate.fromCertificateArn(this, 'cert', CERTIFICATE_ARN);
    const service = new ApplicationLoadBalancedFargateService(this, 'service', {
      cluster,
      taskDefinition,
      certificate,
      domainName: '...',
      domainZone: HostedZone.fromHostedZoneAttributes(this, 'zone', { ... }),
      listenerPort: 443,
    })

What cdk synth produces for the service (note the "ContainerPort": 8080,):

    "serviceService8587F09F": {
      "Type": "AWS::ECS::Service",
      "Properties": {
        "Cluster": {
          "Ref": "ClusterEB0386A7"
        },
        "DeploymentConfiguration": {
          "MaximumPercent": 200,
          "MinimumHealthyPercent": 50
        },
        "DesiredCount": 1,
        "EnableECSManagedTags": false,
        "HealthCheckGracePeriodSeconds": 60,
        "LaunchType": "FARGATE",
        "LoadBalancers": [
          {
            "ContainerName": "AppContainer",
            "ContainerPort": 8080,
            "TargetGroupArn": {
              "Ref": "serviceLBPublicListenerECSGroupD194ED9A"
            }
          }
        ],
        "NetworkConfiguration": {
          "AwsvpcConfiguration": {
            "AssignPublicIp": "DISABLED",
            "SecurityGroups": [
              {
                "Fn::GetAtt": [
                  "serviceServiceSecurityGroup94D21C42",
                  "GroupId"
                ]
              }
            ],
            "Subnets": [
              {
                "Ref": "VpcPrivateSubnet1Subnet536B997A"
              },
              {
                "Ref": "VpcPrivateSubnet2Subnet3788AAA1"
              }
            ]
          }
        },
        "TaskDefinition": {
          "Ref": "TaskDefinitionB36D86D9"
        }
      },
      "DependsOn": [
        "serviceLBPublicListenerECSGroupD194ED9A",
        "serviceLBPublicListener924DC596"
      ],
      "Metadata": {
        "aws:cdk:path": "CdkFargateElbStack/service/Service/Service"
      }
    },

[piradeepk]

@lbjay Great question! ApplicationLoadBalancedFargateService does not directly allow users to use taskdefinitions with multiple port mappings. You can create an ApplicationLoadBalancedFargateService and then add port mappings and add a new listener to the load balancer.

We recently merged in a new pattern which supports multiple target groups/port mappings https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-ecs-patterns/lib/fargate/application-multiple-target-groups-fargate-service.ts

[piradeepk]

@lbjay Please let us know if this does not solve your issue.

[lbjay]

Thanks! It turns out #4107 (just landed in v1.2.0) was exactly what I needed.