AWS boundary
Cluster endpoint, IAM access, IRSA or Pod Identity and KMS.
Cloud security
Amazon EKS security review
Assess EKS control-plane settings, AWS identities, Kubernetes policy and workload isolation together. Reduce cloud attack paths without making routine engineering depend on a security ticket.
01 / Scope
Work on the system, not around it.
The engagement starts with the architecture and working constraints already in place. We agree the risky paths, make the changes visible and leave ownership with the team running the system.
Kubernetes boundary
RBAC, admission, pod security and service accounts.
Workloads
Images, secrets, capabilities, network policy and egress.
Operations
Audit evidence, upgrades, detection, backup and recovery.
02 / Method
Reduce cloud attack paths without making routine engineering depend on a security ticket.
Scope and access are agreed before the work begins. Decisions, changes and residual risk remain visible throughout the engagement.
Map the boundary
Start with evidence, owners and the constraints that shape the safe solution.
Validate the risky paths
Prioritise by practical impact and implement with the people who operate the system.
Implement and verify
Test the changed path, document the decision and hand over a backlog that still makes sense.
03 / What remains
- 01EKS architecture and access map
- 02AWS and Kubernetes findings
- 03Terraform and manifest fixes
- 04Retest and cluster operating notes
Related work
Continue with the adjacent problem.
04 / Talk to Gritt
What is happening in the system?
Send the cloud, workload or deadline. An engineer will reply and tell you whether this is the right scope.
email