Aechdi EKS
You set up an aechdi eks cluster by linking identity roles to Kubernetes roles. You then assign those roles to namespaces or the whole cluster. Most teams start by giving developers broad admin rights to move fast. Broad permissions let anyone read secrets or run commands in live pods. That creates a huge risk when someone makes a mistake or loses a key. How native permissions work in an aechdi eks setup Kubernetes uses role-based rules to control who can do what on the API server. Every rule
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You set up an aechdi eks cluster by linking identity roles to Kubernetes roles. You then assign those roles to namespaces or the whole cluster. Most teams start by giving developers broad admin rights to move fast. Broad permissions let anyone read secrets or run commands in live pods. That creates a huge risk when someone makes a mistake or loses a key.
How native permissions work in an aechdi eks setup
Kubernetes uses role-based rules to control who can do what on the API server. Every rule in this system is additive, which means there are no deny rules. You start with zero access and add rules for specific actions and resources. A Role sets permissions inside one single namespace for your team. A ClusterRole sets rules across the whole cluster for all namespaces. It also covers cluster-wide objects like nodes and non-resource endpoints.
After you write a Role or ClusterRole, you must bind it to a user. A RoleBinding gives a user or group permissions inside one specific namespace. That RoleBinding can point to a local Role or a shared ClusterRole. If you want to grant access everywhere, you use a ClusterRoleBinding instead. A ClusterRoleBinding gives that user permissions across every namespace in the cluster. Teams use this structure to separate dev namespaces from live production workloads.
Kubernetes also uses subresources to control deeper actions on pods. The API writes these subresources with a slash in the resource name. For example, reading pod logs or running commands inside a pod uses subresources. You must grant permissions for the pod log subresource to let someone read logs. You must grant the pod exec subresource to let someone open a shell. This lets you allow log reading while blocking shell access in production.
What native roles solve and what they leave open
Native roles and bindings are great at controlling who can reach the cluster API. They let you lock down namespaces so teams only see their own apps. You can block developers from deleting nodes or changing cluster-wide settings. You can also separate read-only users from admins who deploy new code.
EKS Access Management: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Still, native Kubernetes rules stop working once a session starts running. If a user has permission to run pod exec, Kubernetes steps back. The API server checks who logs in, not what commands run inside the shell. Once inside a container, an engineer can run any script or read local files. They can also query connected databases and pull raw emails or card numbers. Native roles cannot pause a dangerous command or mask phone numbers in flight.
Why static cluster keys and broad roles create risk
Teams often map one cloud role to a broad ClusterRoleBinding to save time. When on-call engineers need to fix a live bug, they get full exec rights. Those rights often stay active long after the ticket closes. If an attacker steals a local token, they inherit that exact same cluster access. Auditing also suffers because you only see that an exec session started. You do not see the exact shell commands or data output from that pod.
Add request guardrails and response masking beside Kubernetes
Cluster roles and service accounts govern who reaches the Kubernetes API. Still, a broad role or agent can delete workloads or print sensitive values from ConfigMaps and logs. In practice, hoop.dev runs beside the API server as a sidecar for your Kubernetes API and checks every request and response alongside RBAC.
With hoop.dev Kubernetes controls, guardrails can allow listing Secret names while refusing reads of Secret data before execution. Data masking redacts matched keys in returned JSON responses and log streams in memory. Furthermore, hoop.dev holds SOC 2 Type II and is MIT licensed on GitHub.
Frequently asked questions
What is the difference between a Role and a ClusterRole in aechdi eks?
A Role applies rules to resources inside a single Kubernetes namespace. A ClusterRole applies rules to cluster-wide objects or across all namespaces at once.
Can I write a deny rule in Kubernetes RBAC?
No, Kubernetes permissions are purely additive and do not support deny rules. To block an action, you must remove the rule that grants that permission.
How do I let a user read pod logs without giving shell access?
Grant the user permission on the pod log subresource inside your Role. Leave out the pod exec subresource so they cannot open a container shell.
Related guides
In this post