Securing Your EKS Cluster with RBAC: Implementing Zero Trust Security Using Role-Based Access Control in Amazon EKS

According to research about 97% of the organizations are using the Public Cloud today and about 83% of the company’s work is now shifted on the cloud Infrastructure ,with increasing Number of organization adopting newer approach to store and deploy their applications Threats and malware are are also increasing their forms , Slight Misconfiguration in the deployment or setup of the environment can lead to Huge Data Loss.

Kubernetes is the most used and reliable Orchestration Tool and even an house hold name for developers as it simplifies many aspects of running a service oriented application infrastructure. API server is considered Core of Kubernetes Control plane as It validates all the resources . All the request sent by Clients first goes to the API server and then any CRUD( create ,Read ,Update ,Delete) operations are allowed after authentication. So if we can filter these incoming request to API server we can almost fully protect our cluster as API Server is called Gateway of the Cluster.

In this Article we will talk how we can Protect our EKS Cluster using Role Back Access Control (RBAC) an authorization step used to validate what and where a user can access Kubernetes Resources.