The order follows this logic:
1. Create the platform (EKS)
2. Define access (IAM)
3. Connect (kubectl)
4. Control permissions (RBAC)
5. Secure (scan)
6. Deploy application
7. Secure network
8. Manage secrets
9. Monitor attacks
10. Automate (GitOps)
1. Create the EKS cluster (the foundation)
Amazon Elastic Kubernetes Service
👉 Why start here?
Because the cluster is the environment where everything runs.
✔️ Without a cluster → no applications, no security, nothing
💡 It’s like creating the “platform” before installing anything.
---
2. Create the IAM role (who can access AWS)
AWS Identity and Access Management
👉 Why now?
Because:
-Kubernetes needs permissions to interact with AWS
-Nodes and services must be authorized
✔️ This defines **who can do what in AWS**
---
3. Access the cluster using `kubectl`
👉 Why here?
Because:
-The cluster exists
-You need a tool to control and manage it
✔️ `kubectl` = your remote control
---
4. Configure RBAC (who can do what inside
Kubernetes)
👉 Why after access?
Because:
-Now you can connect to the cluster
-You must control user permissions inside Kubernetes
✔️ RBAC = internal security
---
5. Scan for vulnerabilities with Trivy
👉 Why before deployment ?
Because:
You must ensure your application is secure before running it
✔️ Detect:
➡️ vulnerable packages
➡️ security issues
💡 Security first, then deployment
---
6. Deploy a Kubernetes application
👉 Why now?
Because:
-The cluster is ready
-Security checks have been done
✔️ You can safely run your app
---
7. Configure Network Policies (network
security)
👉 Why after deployment?
Because:
-Now Pods exist
-You must control who can communicate
✔️ Example:
➡️ allow only necessary traffic
➡️ block everything else
---
8. Create a Kubernetes Secret
👉 Why here?
Because:
The application needs **sensitive data**
✔️ Example:
➡️ passwords
➡️ API keys
💡 Never store secrets in plain text!
---
9. Detect attacks with Falco
👉 Why now?
Because:
-The application is running
-You need runtime security
✔️ Falco detects:
➡️ suspicious behavior
➡️ attacks in real time
---
10. GitOps deployment with Argo CD
👉 Why last?
Because:
-Everything is already working
-Now you automate deployments
✔️ Benefits:
➡️ continuous deployment
➡️ version control
➡️ consistency
-Create the EKS cluster :
-EKS cluster created + Active status :
-Kubernetes permissions management — Create the IAM role :
-Access the cluster using `kubectl` :
-Perform vulnerability scanning with Trivy :
-Deploy a Kubernetes application :
-Create a Kubernetes Secret :
Copyright © All rights reserved.