ReleaseBytes
aws AWS Containers Blog ·

Migrate EC2 apps to EKS Auto Mode with Kiro CLI and MCP servers

bloginfraawsengineeraws-ec2aws-eks
announcement

This post demonstrates how to migrate a Node.js application from Amazon EC2 to Amazon EKS Auto Mode using the Kiro CLI and MCP servers. EKS Auto Mode simplifies compute provisioning, autoscaling, and node lifecycle management. The migration process uses specialized MCP servers and Kiro CLI to automate tasks from Dockerfile creation to production deployment on EKS Auto Mode, reducing complexity and accelerating timelines.

  • →Automated migration tools reduce complexity
  • →Streamlined migration path with EKS Auto Mode
  • →Practical migration scenario walkthrough
  • →Architecture comparison: EC2 vs. EKS Auto Mode
  • →Security posture shifts from instances to pods
Features (1) ›
  • Automated migration tools reduce complexity

    AWS Model Context Protocol (MCP) Server, specialized Amazon EKS MCP Server, AWS Knowledge MCP Server, and Kiro CLI reduce the complexity of migrating from EC2 to EKS by providing automated workflows for containerization and deployment orchestration.

Notes (5) ›
  • Streamlined migration path with EKS Auto Mode

    Amazon EKS Auto Mode handles compute provisioning, autoscaling, node lifecycle, networking, cluster DNS, storage, load balancing, and GPU support, allowing teams to interact with Kubernetes primitives while EKS Auto Mode manages underlying infrastructure.

  • Practical migration scenario walkthrough

    The post details a practical scenario migrating a Node.js web application from EC2 instances to EKS Auto Mode, covering configuration and use of AWS and Amazon EKS MCP Servers with Kiro CLI to automate tasks like Dockerfile creation, image optimization, Kubernetes manifest generation, and production deployment.

  • Architecture comparison: EC2 vs. EKS Auto Mode

    The initial EC2 architecture involves traditional virtual machine deployment with infrastructure management, while the target EKS Auto Mode architecture replaces the EC2 compute layer with EKS Auto Mode, enabling automatic scaling and minimal infrastructure management, using Amazon ECR for container images.

  • Security posture shifts from instances to pods

    EKS Auto Mode shifts the security boundary from instances to pods and containers, with changes in IAM credentials (Instance profile vs. EKS Pod Identity), network isolation (Security groups vs. Pod security groups and Network Policies), image supply chain (Custom AMIs vs. ECR scanning), runtime security, and secrets management.

  • Benefits of EKS Auto Mode over EC2

    EKS Auto Mode eliminates manual responsibilities like scaling policies, AMI updates, and capacity planning found in EC2 self-management, offering automatic capacity planning, transparent node patching and upgrades, faster scaling, and cost optimization through bin-packing and Spot instance support.

Read the original announcement →

https://aws.amazon.com/blogs/containers/migrate-amazon-ec2-to-eks-auto-mode-using-kiro-cli-and-mcp-servers/

Related releases