Nice to be able to deploy multiple containers via LoadBalancedFargateService

• 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

You can deploy only one docker image when you are using ecsPatterns.LoadBalancedFargateService

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

It’ll be nice to be able to deploy multiple images (a la docker-compose) within a service.

ESC-CLI, for example, currently provides a way to include multiple container images through a docker-compose file.

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

Make the API, LoadBalancedFargateService, more useful.

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

• https://github.com/aws/amazon-ecs-cli

[piradeepk]

@realharry you can actually add multiple containers after constructing the LoadBalancedFargateService by using the addContainer method within a taskDefinition.

It would look something like:

const fargateService = new LoadBalancedFargateService(...)
fargateService.service.taskDefinition.addContainer(containerName, {
    image: new ecs.AssetImage(path.join(__dirname, '..', 'demo-image'))
})

The LoadBalancedFargateService exposes the FargateService (service), and the FargateService (service) exposes the FargateTaskDefinition(taskDefinition) which allow you to add a container to a Task Definition.

Feel free to let me know if you have any issues with the above.

[jgoux]

Hello @piradeepk and thanks for the addContainer tip.

Initially I wanted to use a docker-compose.yaml containing two services. I use depends_on and service_healthy to start one service only when the other is up. Seems like your solution doesn’t cover such use case.

Also, only one of the two services needs to be exposed to the ALB.

Can the current API handle my use case?