our_eks_to_ecs_migration_chronicle.pdf

Transcript

1. Our EKS to ECS Migration Chronicle Kosuke Ozawa [AWS Community Builder - Containers]
2. Today’s Agenda 1. Background 2. Challenges in Migration Planning 3. Solution Approach 4. Conceptual Differences between EKS and ECS 5. Implementation Challenges 6. Current Learnings and Future Expectations
3. Self-Introduction Name Kosuke Ozawa Position Systems Architect Favorite AWS Service Amazon ECS Amazon ECS
4. Background Operating a web system on EKS → Considering migration to ECS Amazon EKS Something awesome 「Delete “K”!」 Amazon ECS
5. Reasons for Considering ECS Migration 1. High operational costs for Kubernetes updates 2. Team’s lack of Kubernetes experience 3. Re-evaluation of Kubernetes necessity 4. Extensive operational experience with ECS
6. Challenges in Migration Planning 1. Lack of clear image for replacing EKS with ECS 2. Difficulty in grasping the overall picture and mitigating risks 3. Need concretize the migration process
7. Solution Approach Identifying conceptual differences between EKS and ECS Designing a provisional architecture and conducting PoC Amazon EKS Amazon ECS Task Task Task
8. Conceptual Differences between EKS and ECS
9. Kubernetes Managed Services vs AWS Container Orchestration Service Node Group Amazon EKS Auto Scaling group EC2 instance Addon Scaling EC2 instance Addon Translate to AWS → Not required with ECS Manage node instances →Alternate with task group Manage node scaling →Same with ECS
10. How to replace Kubernetes with ECS tasks Service Task ECS Service Connect Event Application LoadBalancer Migrate Kubernetes to ECS （Example...）
11. Kubernetes All-in-One vs ECS + Other AWS Services EKS（Kubernetes） ECS Combination of components Combination of ECS and other AWS services Deployment, Ingress, Service, Job, Statefulset, CRD, etc... Functionality realized through ECS and other AWS services
12. Example 1: Web Application Service Application LoadBalancer AWS Auto Scaling Task Definition ParameterStore
13. Example 1: Web Application（Ing - Pod） Service Application LoadBalancer
14. Example 1: Web Application(Deploy, HPA) Service AWS Auto Scaling Task Definition Parameter Store
15. Example 2: Cron Job Task Event Task Definition Parameter Store
16. Implementation Challenges
17. Choosing between Fargate and EC2 Consideration from performance and operational perspective Taking into account network mode constraints Amazon EC2 AWS Fargate
18. Public Access Method in awsvpc Mode No ENI provided with public IP address in EC2 awsvpc mode Public subnet Amazon ECS Instance Internet
19. Scaling Interval EKS ECS Horizonal Pod Autoscaler（HPA） Application AutoScaling using CloudWatch metrics Default 15-second interval Default 1-minute interval（for Fargate）
20. Scaling Interval AWS Auto Scaling Container Insights OR ADOT (AWS Distro for OpenTelemetry)
21. Current Learning and Future Expectations 1. Deepening understanding of containers and microservices 2. Potential for reducing operational costs and improving quality 3. Strengthening ability to address technical challenges
22. Summary Identifying conceptual differences between EKS and ECS • How to replace Kubernetes with ECS tasks • After understanding Kubernetes configuration patterns, replace them with the optimal design patterns for AWS Designing a provisional architecture and conducting PoC • Choose a platform based on performance and operational considerations, as well as network mode constraints • Recognize differences in horizontal scaling evaluation intervals and consider the best method
23. Thank you for your attention.