aws / containers-roadmap

This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
https://aws.amazon.com/about-aws/whats-new/containers/
Other
5.22k stars 321 forks source link

[ECS] [request]: Support Sidecar Containers on AWS Batch Task #1522

Open johnrk-zz opened 3 years ago

johnrk-zz commented 3 years ago

Community Note

Tell us about your request Please allow support sidecar containers on AWS Batch Task.

Which service(s) is this request for? ECS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? The lack of sidecar container support for AWS Batch is causing AWS Batch to have issues with its auto-scaling.

Are you currently working around this issue? Users are currently required to run Datadog Agent as a daemon service. With this setup, users are having issues with AWS Batch properly auto-scaling.

Additional context This is for Datadog users.

Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

johnrk-zz commented 3 years ago

In addition to this feature request, do you all plan to support AWS Firelens with AWS Batch?

There does not appear to be any documentation about it.

nathanhruby commented 2 years ago

Sidecars are useful for a number of reasons, not just data dog. In our case we are trying to use a external provided sidecar from an OSS project instead of building project and the language ecosystem into our app container and runtime.

laureanopiotti commented 2 years ago

+1

anybodysguest commented 1 year ago

Would love to have this feature. I currently do a lot of work with Fargate and use multiple containers per task regularly. It would be great to have the Fargate-flavor of AWS batch be able to use sidecars. In fact, it would be downright amazing. :)

ecoupal-believe commented 8 months ago

@johnrk-zz, same problem here with datadog, did you find any workaround ?

adamantike commented 8 months ago

I assume this should now be possible after yesterday's announcement: AWS Batch now offers multi-container jobs

Erry91 commented 3 months ago

It seems possible to define more than one container in one job definition, however it seems that port mapping is not available (it would be needed for example if one wants to configure a Xray daemon as a sidecar container). Did anyone give it a look?