Figuring It Out — Kubernetes, EKS, AWS | #3 — Role-Based Access Control (RBAC)

In the last two chapters, we have been mostly occupied with the initial setup of EKS, along with initial monitoring tools for understanding our cluster better. What about onboarding our teammates onto our EKS Kubernetes cluster, and assigning different groups of teammates the appropriate access rights? Let’s explore that today!

(Here’s the ongoing series — both old and new content. Clone the project at the correct tag to receive content up to that stage):

Role-Based Access Control (RBAC)

In line with the theme of security, RBAC represents the idea of assigning permissions to users through “roles”, and not exposing access to your tools publicly for all. These “roles” can represent different actual roles and functions in your company, such as DevOps engineers and Backend engineers.

Why is RBAC important?

Through these assigned “roles”, different users can gain the appropriate level of read and write access to tools…