開發者無伺服器、容器技術專題 Introducing Amazon Fargate (Level 200) Speaker: KC Liang, BDM, AWS Guest Speaker: Keith Yang, Senior Cloud Engineer, iCHEF

1. Introduction
To Amazon Fargate
KC Liang
Business Development
Time: 40 min
Level: 200

2. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
OUR JOURNEY!

3. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

4. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
BUILDING AN ECOSYSTEM

5. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
WHY DO WE LOVE CONTAINERS?
Packaging Distribution Immutable
infrastructure

6. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
HELPING CUSTOMERS SCALE
CONTAINERS
450+%
growth
Hundreds of millions
of containers started each week
millions
of container instances

7. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
PRODUCTION WORKLOADS ON AWS
AWS VPC
networking mode
Advanced task
placement
Deep integration
with AWS services
ECS CLI…{ }
Global footprint
Powerful scheduling
engines
Auto scaling
CloudWatch metrics
Load balancers

8. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
CUSTOMERS ARE OUR KEY!
50+
releases
since 2015
Customers
Release
Feedback /
New Use
Cases
Learn
Experiment,
Innovate,
& Build
Features

9. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
ENABLE FOCUS ON APPLICATIONS

10. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
INTRODUCING FARGATE!

11. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
CHANGING COMPUTE CONSUMPTION
MODEL
No instances
to manage
Task
native API
Resource
based pricing
Simple, easy to use,
powerful – and new
consumption model
=

12. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
PRODUCTION WORKLOADS ON AWS
AWS VPC
networking mode
Advanced task
placement
Deep integration
with AWS services
ECS CLI…{ }
Global footprint (in 2018)
Powerful scheduling
engines
Auto scaling
CloudWatch metrics
Load balancers

13. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
EKS SUPPORT FOR FARGATE IN 2018

14. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
MICROSERVICES

15. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
BATCH JOBS

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
MIGRATION TO THE CLOUD

17. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
HOW DO I RUN CONTAINERS
ON FARGATE?

18. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
RUNNING CONTAINER

19. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
EC2 Instance
TaskTask
Task Task
EC2 Instance
TaskTask
Task Task
EC2 Instance
TaskTask
Task Task
EC2 Instance
TaskTask
Task Task
EC2 Instance
TaskTask
Task Task
RUNNING CONTAINERS

20. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Scheduling and Orchestration
Cluster Manager Placement Engine
RUNNING CONTAINERS AT SCALE WITH ECS
Availability Zone #1 Availability Zone #2 Availability Zone #3

21. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
ECS
AMI
Docker
agent
ECS
agent
ECSTaskECSTask
ECSTaskECSTask
EC2 Instance

22. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Scheduling and Orchestration
Cluster Manager Placement Engine
ECS
AMI
Docker
agent
ECS
agent
EC2 Instance
ECS
AMI
Docker
agent
ECS
agent
EC2 Instance
ECS
AMI
Docker
agent
ECS
agent
EC2 Instance

23. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
RUNNING FARGATE CONTAINERS WITH
ECS

24. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Define application containers: Image
URL, CPU & Memory requirements,
etc.
register
Task Definition
create
Cluster
• Infrastructure Isolation boundary
• IAM Permissions boundary
run
Task
• A running instantiation of a
task definition
• Use FARGATE launch type
create
Service
Elastic Load
Balancer
• Maintain n running copies
• Integrated with ELB
• Unhealthy tasks automatically
replaced
ECS CONSTRUCTS

25. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
TASK DEFINITION
{
"family": “scorekeep",
"containerDefinitions": [
{
"name":“scorekeep-frontend",
"image":"xxx.dkr.ecr.us-east-1.amazonaws.com/fe"
},
{
"name":“scorekeep-api",
"image":"xxx.dkr.ecr.us-east-1.amazonaws.com/api"
}
]
}
Immutable, versioned document
Identified by family:version
Contains a list of up to 10 container definitions
All containers are co-located on the same host
Each container definition has:
• A name
• Image URL (Amazon ECR or Public
Images)
• And more…stay tuned!
Task Definition Snippet

26. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
RUNNING FARGATE CONTAINERS WITH
ECS
Use ECS APIs to launch Fargate Containers
Easy migration – Run Fargate and EC2 launch
type tasks in the same cluster
Same Task Definition schema

27. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
NETWORKING

28. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
VPC INTEGRATION 172.31.0.0/16
Subnet
172.31.1.0/24
Internet
Other Entities in VPC
EC2 LB DB etc.
Private IP
172.31.1.164
• AWS VPC Networking Mode – each task gets
its own interface
• All Fargate Tasks run in customer VPC and
subnets
• Configure security groups to control inbound &
outbound traffic
• Public IP support
• Spread your application across subnets in
multiple Availability Zones (AZs) for resiliency
us-east-1a
us-east-1b
us-east-1c
ENI Fargate
TaskPublic /
208.57.73.13 /

29. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
LOAD BALANCING
APPLICATION LOAD BALANCER
NETWORK LOAD BALANCER

30. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
SECURITY

31. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
CLUSTER LEVEL ISOLATION
PROD Cluster Infrastructure
DEV Cluster Infrastructure
BETA Cluster Infrastructure
QA Cluster Infrastructure
Web Web
Shopping
Cart
Shopping
Cart
Notifications NotificationsWeb
Shopping
Cart NotificationsWeb
Shopping
Cart
Shopping
Cart
Notifications NotificationsWeb Web
PROD CLUSTER BETA CLUSTER
DEV CLUSTER QA CLUSTER

32. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
PERMISSION TIERS
Cluster
Permissions
Application
Permissions
Task
Housekeeping
Permissions
Cluster
Fargate Task
Cluster Permissions:
Who can run/see tasks in the cluster?
Application (Task) Permissions:
Which of my AWS resources can this application access?
Housekeeping Permissions:
What permissions do I want to grant ECS to perform?
e.g.
• ECR Image Pull
• CloudWatch Logs pushing
• ENI creation
• Register/Deregister targets into ELB

33. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
CONTAINER REGISTRIES

34. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
REGISTRY SUPPORT
3rd Party Private Repositories (coming soon!)
Public Repositories supported (DockHub)
Amazon Elastic Container Registry (ECR)

35. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
VISIBILITY AND MONITORING
Service-level metrics available
CloudWatch Logs
CloudWatch Events supported

36. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
STORAGE
Container Storage Space – 10GB
Ephemeral storage backed by EBS
Shared volume space for containers within the
task – 4GB

37. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
CONFIGURATIONS & PRICING

38. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
PRICING DIMENSIONS
{
”cpu": “1 vCPU”,
”memory": “2 gb”,
"networkMode": ”AWSVPC",
"compatibilities": [”FARGATE",
”EC2"],
"placementConstraints": [],
"containerDefinitions": [
{
<snip>…....
Task level resources
• Configurable independently (within a range)
Dimensions: Task level CPU and memory
Per-second billing
Task
Level
Resources

39. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
TASK CPU & MEMORY CONFIGURATIONS
Flexible configuration options –
50 CPU/memory configurations
CPU Memory
0.25 vCPU 512MB*, 1GB, 2GB
0.5 vCPU 1GB to 4GB (1GB increments)
1 vCPU 2GB to 8GB (1GB increments)
2 vCPU 4GB to 16GB (1GB increments)
4 vCPU 8GB to 30GB (1GB increments)

40. CLOUDFORMATION SUPPORT

41. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
99.99%
© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

42. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

43. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

44. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
ECS Instance ECS Instance ECS Instance ECS InstanceECS Instance ECS Instance
EC2
FARGATE
Notifications
Amazon ECS CLUSTER
Availability Zone #1 Availability Zone #2 Availability Zone #3
Subnet 2
172.31.2.0/24
Subnet 1
172.31.1.0/24
Subnet 3
172.31.3.0/24
Web
Shopping
Cart

45. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
EARLY ADOPTERS

46. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
PARTNER INTEGRATIONS

48. Amazon ECS
at iCHEF
Keith Yang
Senior Cloud Engineer

49. About Me
Keith Yang
Senior Cloud Engineer at iCHEF
Founder and co-organizer of Taipei.py
Web Lead of PyCon Taiwan 2018
Chairperson of PyCon APAC 2015

50. About iCHEF
• 成立於 2012
• 用科技讓開餐廳成為一門更好的生意

51. iCHEF POS：餐廳經營的解決方案
• 從來電預約與訂位，客人到餐
廳的侯位、外帶
• 點餐、出給廚房與吧台的單
• 顧客關係管理、折折管理與集
點集點方案到營運分析報表

52. iCHEF POS 的用量
• 3200 家餐廳採用
• 每月 340 萬筆交易
• 每月處理 14 億元交易

53. iCHEF 後端系統的用量
• 每日 250 萬 API request
• 尖峰期每分鐘 3500 API request
• Web server + API server
+ Background job worker + Cron tasks

54. Infrastructure as Code
• 需要許多不同的環境來進行測試、開發和實際的服
• 功能測試環境、整合測試環境、線上服務架構調
• 希望能讓每個環境都有一樣的系統架構
• 希望能夠對整個環境做版本控制

55. Infrastructure as Code (cont.)
• 用程式產生參數化的 CloudFormation
範本
• 建立 VPC、ASG、ALB 與 ECS Cluster

56. Before: Manual Deployment
• 每次得手動設定新的
ALB & Stack
• 難以掌握每個環境
不同的參數與設定
• 不易展開新的 Stack

57. Now with CloudFormation
使用 CloudFormation 來自動化部屬
ALB & Stack 的建立與更新

58. Now with CloudFormation (cont.)
• 編寫 CloudFormation 快速建立 ALB &
Stack
• 掌握每個環境不同的參數與設定

59. One Click Deploy
• 使用 Jenkins
build Docker image
• 使用 ECR 來儲存 image
• 在 ECS 上進行
rolling update

60. Before: Self-host & deploy Docker
• 需要應用程式開發者熟悉 Docker build 的細節
• 需要自行維護 Docker Registry 的機器
• 複雜而手動的設定增加溝通成本與設錯的機會

61. After: ECS & ECR
• 應用程式開發者無需分心於不同環境的部屬
• 不用自行維護 Docker Registry 的機器
• 簡單而自動的設定 ➡ 節省溝通成本並減少設錯
的機會

62. 依流量來動態擴展服務
• 餐廳有很明顯的尖峰時刻
• 使用 Auto Scaling 做動態
服務修改
• 使用較多的 Cluster Status
來處理 EC2 Scaling

63. Before: Manual Scaling
• 需要猜好猜滿要用多少 instance，
對預期外的需求不易立即回應
（例如：平常週末的忽然高峰用量）
• 常需要手動調整並分配各個 ECS Task 的用
量

64. Now with Auto-scaling
• 不用怕猜錯餐廳服務的用量，用多少開多少
• 對預期外的需求可以立即回應
• 自動分配各個 ECS Task 的用量
• 還是要從大範圍的 EC2 設定（猜）基本用量與最大用
量

65. 使用 ALB 來提高系統穩定度
• API 有快有慢，個別需要不同的設定；
傳統的 ELB 無法輕易配置出來
• 免去申請與設定 HTTPS（SSL 憑證）的苦痛
• 使用 ALB 的 path based routing 來讓不同的 ECS
Service 處理耗時不同的 API

66. 不同的 API 反應
• 慢的 API：上傳、下
載報表或當日總結單
• 快的 API：一般的
request，如登入、點
餐、管理介面

67. 定期排程工作
• 每天都有一些定期的排程工作，像是寄送每天
的營業狀況給客戶
• 使用 Scheduled task 來處理，降低系統複雜
• 需預留 EC2 的容量

68. Fargate 的繼往開來
• 提供以上 ECS、ECR、Auto-scaling 與
ALB 等優點
• Clicks to Deploy，直接幫忙建立
CloudFormation template

69. 能用 Fargate 來大幅降低管理成本
• 創建環境時
不再手動處理 EC2 配置
• 流量增加時
只要 scale Task 即可
• 不再需要為 Scheduled Task 預留空間

70. Thank You