Use multiple clusters to separate tenant workloads

The most secure way to run Silo workloads on EKS is to create a distinct EKS cluster for each tenant. In such a design, even a tenant that runs privileged containers and has access to the hosts cannot impact other tenants. Care must still be taken to not provide credentials related to other tenants on a different cluster, and other AWS security best practices such as proper Security Group rules, virtual private cloud (VPC) separation, or both must be implemented.

This approach does have some disadvantages. Having a separate cluster for each tenant will add more complexity to the operational footprint of your environment. While you can automate much of the operational experience, this approach will impact the efficiency, agility, and cost profile of your SaaS environment.