Interview AWS

What are managed node groups versus self-managed nodes versus Fargate on EKS?

AWS · Intermediate level

Answer

Managed node groups simplify EC2 worker lifecycle, self-managed nodes give more control, and Fargate runs pods without node management but with constraints. I often mix them based on workload control, cost, and operational needs.

Technical explanation

Fargate reduces node management but does not support every daemonset, privileged, storage, or networking pattern.

EKS is managed Kubernetes, not no-ops Kubernetes: IAM, networking, add-ons, node strategy, upgrades, RBAC, policies, and workload reliability remain customer responsibilities.

Workload identity, private networking, image security, ingress standards, autoscaling, and observability are foundational controls for production clusters.

Troubleshooting EKS requires separating control-plane, node, CNI, scheduler, ingress, and application failure domains.

Hands-on example

1. Create or use an EKS sandbox cluster with private subnets, managed add-ons, workload IAM, and a sample namespace.

2. Deploy a small container from ECR using Kubernetes manifests or Helm, with readiness/liveness probes and resource requests.

3. Add ingress/load balancing, pod IAM, logging, metrics, and network/security controls relevant to the question.

4. Test node replacement, pod rescheduling, image pulls, access control, and rollback.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More AWS interview questions

← All AWS questions