site-logo

JAWS PANKRATION 2024

site-logo
HomeNewsTimetableCfPCommitteePromotionFollow UpPrivacy Policy

Our EKS to ECS Migration chronicle

Lv300

Lv300

8/24/2024 13:00 (UTC)
Session Info

I went through trial and error to migrate a web system running on Amazon EKS to Amazon ECS. (I'm still processing!)

I'll talk about the issues to be considered due to the conceptual differences between EKS and ECS, and the implementation issues that emerged during PoC.

Kosuke Ozawa

Kosuke Ozawa

- AWS Community Builders -

- AWS All Certified Engineers(APN) -

Session Category
Container
AWS Services
Amazon EKS
Amazon ECS
Session Materials
    Session Archive
    Session Summary (by Amazon Bedrock)
      The speaker discusses the migration plan from Amazon EKS to Amazon ECS, focusing on the design phase of an ongoing project. They highlight the challenges and approaches in container orchestration migration. Current situation: - Operating web systems with high maintenance costs - Lack of experience with EKS among team members - ECS expertise within the team Challenges: - Difficulty in visualizing the transition from EKS to ECS - Risk management - Need for a concrete migration process Strategy: 1. Identify conceptual differences between EKS and ECS 2. Design interim configuration for proof of concept Key points: - EKS is a managed Kubernetes service, while ECS is AWS's container orchestration service - Most EKS functions can be replicated in ECS - Focus on replacing EKS pods with ECS tasks Implementation challenges: - Choosing between Fargate and EC2 for ECS (selected Fargate) - Addressing horizontal scaling evaluation intervals Learnings: - Improved understanding of containers and microservices - Potential for reduced operational costs and improved quality - Enhanced team communication and technical problem-solving skills The migration plan has provided valuable insights into the differences between EKS and ECS, including network and scaling nuances. The project represents a significant technical challenge and growth opportunity for the team, which will inform future design and implementation phases.

    Back

    ©JAWS-UG (AWS User Group - Japan). All rights reserved.