AWS SSA Webinar 13 - Getting started on AWS with Containers: Amazon ECS
Download as PPTX, PDF0 likes153 views
This document provides a summary of a webinar on getting started with Amazon ECS, covering topics such as creating a cluster, deploying with Amazon CodePipeline, and managing capacity with EC2 and AWS Fargate. It details the infrastructure requirements and gives insights into instance types and their contributions to total capacity. Additionally, it discusses API parameters for mixed instance policies and the ECS agent setup.
![© 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
API parameters
"MixedInstancesPolicy": {
"LaunchTemplate": {
"LaunchTemplateSpecification": {
"LaunchTemplateName": "MyLaunchTemplate"
},
"Overrides": [
{
"InstanceType": "m4.xLarge",
"WeightedCapacity": "1"
},
{
"InstanceType": "m4.2xLarge",
"WeightedCapacity": "2"
},
{
"InstanceType": "m4.4xLarge",
"WeightedCapacity": "4"
}
]
},
"InstancesDistribution": {
"OnDemandAllocationStrategy": "prioritized",
"OnDemandBaseCapacity": 10,
"OnDemandPercentageAboveBaseCapacity": 50,
"SpotAllocationStrategy": “capacity-optimized",
"SpotInstancePools": 2
}
}
AZ1 and AZ2
Desired
Min
Max
On-Demand base
50% On-Demand
50% Spot
Minimum On-Demand (10)](https://image.slidesharecdn.com/2020-05-26awswebinar13-gettingstartedonawswithcontainersecs-200527090837/85/AWS-SSA-Webinar-13-Getting-started-on-AWS-with-Containers-Amazon-ECS-7-320.jpg)
AWS SSA Webinar 13 - Getting started on AWS with Containers: Amazon ECS
- 1. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Getting started on AWS with Amazon ECS O n l i n e W e b i n a r – 2 0 2 0 / 0 5 / 2 6 Cobus Bernard Sr Developer Advocate Amazon Web Services @cobusbernard cobusbernard cobusbernard
- 2. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Agenda Creating a cluster Deploy using Amazon CodePipeline Using Amazon EC2 hosts vs AWS Fargate Capacity Providers Autoscaling using Spot and On-Demand Q&A
- 3. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 4. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Infrastructure required Subnet Subnet VPC Availability Zone US-EAST-1A Subnet Subnet Availability Zone US-EAST-1C
- 5. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 6. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. m4.xlarge Spot Weight of 1 m4.2xlarge Spot Weight of 2 m4.4xlarge On-Demand Weight of 4 Availability Zone 1 Availability Zone 2 Availability Zone 3 Different instance types contribute differently to total capacity Now: Spot, On-Demand, and RIs in a single ASG with weights
- 7. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. API parameters "MixedInstancesPolicy": { "LaunchTemplate": { "LaunchTemplateSpecification": { "LaunchTemplateName": "MyLaunchTemplate" }, "Overrides": [ { "InstanceType": "m4.xLarge", "WeightedCapacity": "1" }, { "InstanceType": "m4.2xLarge", "WeightedCapacity": "2" }, { "InstanceType": "m4.4xLarge", "WeightedCapacity": "4" } ] }, "InstancesDistribution": { "OnDemandAllocationStrategy": "prioritized", "OnDemandBaseCapacity": 10, "OnDemandPercentageAboveBaseCapacity": 50, "SpotAllocationStrategy": “capacity-optimized", "SpotInstancePools": 2 } } AZ1 and AZ2 Desired Min Max On-Demand base 50% On-Demand 50% Spot Minimum On-Demand (10)
- 8. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 9. ECS agent Docker agent OS Amazon Elastic Compute Cloud (Amazon EC2) instance ECS agent Docker agent OS EC2 instance ECS agent Docker agent OS EC2 instance Amazon Elastic Container Service (Amazon ECS)
- 10. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.
- 11. Thank you! © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved. Cobus Bernard Sr Developer Advocate Amazon Web Services @cobusbernard cobusbernard cobusbernard
Editor's Notes
- #7: Introducing instance type weights Configure weight to scale in and out based on previous gen instances or vCPUs across multiple AZs Distribute Capacity evenly between availability zones for On-Demand and Spot separately
- #8: <Including these to explain in more detail how this split / balance works> Overrides let you specify additional instance types to consider