Allow container side-cars AKA multiple containers per service.

dmarkey commented 2 years ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request What do you want us to build?

Allow multiple containers in a single service .

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Anything else we should know?

Just like in kubernetes with a Pod can have multiple containers that are needed to solve a particular business problem.

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

toricls commented 2 years ago

Hi @dmarkey, would you possibly tell us what side-cars do you want to run today?

dmarkey commented 2 years ago

For example, a django app would routinely be deployed with 2 containers, one with uwsgi(application server) and one nginx(static assets). This is pretty common.

toricls commented 2 years ago

Thanks! I'm not a python guy but any reason that you don't use CF + S3 for static assets instead of returning them from containers?

dmarkey commented 2 years ago

This is just one example.. loads of use-cases for sidecars.

andymac4182 commented 2 years ago

This is the same for PHP Laravel applications Nginx+PHP-FPM as two containers. We have a few clients who are doing this and would benefit from apprunner

CarlosDomingues commented 2 years ago

@toricls

1 - Integrations. It would be possible to connect apps with App Mesh (Envoy), X-Ray (daemon) and Secrets Manager (Dapr backend) without waiting for native integrations.

2 - Language agnostic composability. It would be possible to implement stuff like oath2 without touching code. I work in a polyglot shop and doing that with Fargate is a huge win for us. We solve our problems once, not for every language and framework.

3 - FOMO. Sidecars are becoming a common pattern with the emergence of K8s and using a platform without support for those might block us from using shiny new technologies.

yngndrw commented 2 years ago

The AWS OpenTelemetry Collector (https://hub.docker.com/r/amazon/aws-otel-collector) is another example usage. I can't see a secure way of using this right now as AppRunner doesn't support VPCs either. The key part is that it isn't just for convenience, a sidecar also allows private communication between the containers.

shaunakv1 commented 2 years ago

drissamri commented 8 months ago

Like mentioned above, integration with OTEL collector, Datadog integrations, Fluentbit sidecar..

aws / apprunner-roadmap

Allow container side-cars AKA multiple containers per service. #71