Falco + Chamber in Fargate
following Kris Nova's advice I'm sharing with you our use case and concerns.
Right now, we are using Fargate to deploy our production workloads with an internal PaaS.
To pass secrets to the containers, we are using Chamber ( https://github.com/
We are overloading the entrypoint with Chamber, who spawns our app with the appropriate secrets in the environment.
After knowing Falco's support for userspace, we mimicked Kris Nova's PoC and we liked how Falco instruments inside Fargate.
Our concern is that Falco is using the same approach as Chamber, so if we want to deploy Falco in our environment we would have like 2 levels of overload. Falco -> Chamber -> App.
We don't know if this is the best approach or how difficult it would be to troubleshoot problems with this approach.
What do you think?
toggle quoted messageShow quoted text
When you say overload you mean building off a pre-existing container image? If it was me I would just bake everything into a base image (Falco and Chamber) and build on that.
We don't have formal support for the userspace components (yet) but if you or anyone else is deeply interested in helping bake this into the pipeline there is an infra working group that would be where I would start. Hope this helps.