No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Is there an easy way using Crosswalk with ECS to specify a container port that is different to the load balancer port of 80?

You can do something like the following:

```const task = new awsx.ecs.FargateTaskDefinition("td", {
  containers: {
    nginx: {
      image: "nginx",
      portMappings: [{protocol: "tcp", containerPort: 80, hostPort: 80}]
    }
  }
})```

yes pretty much! Thanks for the reply. So my container runs on port 5000

```const alb = new awsx.lb.ApplicationLoadBalancer("backend-ecs-alb");
const listener = alb.createListener("backend-ecs-listener", { port: 80 });

const nginx = new awsx.ecs.FargateService("backend-ecs", {
    taskDefinitionArgs: {
        containers: {
            backend: {
                image: image,
                memory: 128,
                portMappings: [listener],
            },
        },
    },
    desiredCount: 2,
});```

do I need to create a specific `FargateTaskDefinition` for this?

```const alb = new awsx.lb.ApplicationLoadBalancer("backend-ecs-alb");
const listener = alb.createListener("backend-ecs-listener", { port: 80 });
const nginx = new awsx.ecs.FargateService("backend-ecs", {
    taskDefinitionArgs: {
        containers: {
            backend: {
                image: image,
                memory: 128,
                portMappings: [{protocol: "tcp", containerPort: 80, hostPort: 80}],
            },
        },
    },
    desiredCount: 2,
});```

There’s no mention of port 5000 above ?

Then you can swap `containerPort` from `80` to `5000`

if I remove `  portMappings: [listener],` from the taskDefinition, how does the LB get bound to the ECS task?

ok well this worked:

```import * as awsx from "@pulumi/awsx";

const image = awsx.ecr.buildAndPushImage("backend-ecs", {
    context: "./app",
});

const cluster = new awsx.ecs.Cluster("backend-ecs-cluster");

const alb = new awsx.elasticloadbalancingv2.ApplicationLoadBalancer("backend-ecs-alb", { 
    external: true,
    securityGroups: cluster.securityGroups 
});
const atg = alb.createTargetGroup("backend-ecs-tg", { 
    port: 5000, 
    protocol: "HTTP",
    deregistrationDelay: 0 
});
const web = atg.createListener("web", { 
    port: 80 
});

const appService = new awsx.ecs.FargateService("backend-ecs-fargateservice", {
    cluster,
    taskDefinitionArgs: {
        container: {
            image: image,
            portMappings: [web],
        },
    },
    desiredCount: 1,
});

export const url = web.endpoint.hostname;```

I was about to say you can use a network loadbalancer:

```const lb = new awsx.lb.NetworkTargetGroup("nginx", { port: 5000 })
                .createListener("listener", {port: 80});```

But your way will work too :slightly_smiling_face: