Multi-container task definition

[kristianeschenburg]

Hi

Thanks for the TF code, it's been helpful for me to learn how to deploy these Dagster pipelines to AWS.

I was curious about your main.tf file. It looks to me like you're creating a single multi-container ECS task definition (with a container for the daemon, webserver, and user code). Is this correct? Is it possible to deploy a pipeline using 3 separate task definitions instead? I'm curious about how these tasks would communicate with each other e.g. what network mode would they use?

[menendes]

Hi Kristian, Thanks for contacting and sorry for late response, I didn't realize your message. Probably you can't do it but I am not sure. I should check it again. Btw why would you like to use separate task definition ? If I understand your use cade maybe I can help. Thanks.

…

On Tue, Oct 29, 2024, 7:11 PM Kristian Eschenburg ***@***.***> wrote: Hi Thanks for the TF code, it's been helpful for me to learn how to deploy these Dagster pipelines to AWS. I was curious about your main.tf file. It looks to me like you're creating a single multi-container ECS task definition (with a container for the daemon, webserver, and user code). Is this correct? Is it possible to deploy a pipeline using 3 separate task definitions instead? I'm curious about how these tasks would communicate with each other e.g. what network mode would they use? — Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJUALZEU7BPDD3PQSR76GFTZ56XTDAVCNFSM6AAAAABQ2HEIY6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGYZDCNZTGA4DKMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>