ECS, Fargate and EKS (Kubernetes on AWS) compared and explained in a nutshell

Amazon's announcement of its new container services, Fargate and EKS (Elastic Kubernetes Service), marks its entry into the managed Kubernetes service space. EKS is a managed service that uses upstream Kubernetes and is designed to run across multiple Availability Zones, utilizing AWS's IAM for RBAC and PrivateLink for secure access. Fargate, on the other hand, allows users to run containers orchestrated by ECS or Kubernetes without managing the underlying EC2 instances, offering flexibility by charging per computing second used. While ECS currently integrates more seamlessly with other AWS services, EKS offers the advantage of utilizing the same scheduler both within AWS and elsewhere. Fargate's approach addresses the complexity of managing container orchestration layers and provides a solution to the bin packaging problem, though it comes with its own cost considerations. However, questions remain about EKS's customization capabilities and its integration with AWS services, as well as the potential costs associated with inter-zone traffic and other resources.