AWS re:Invent 2019: [NEW LAUNCH!] Enabling application-first thinking with Amazon ECS (CON325-R1)

Getting started with containerized application development often requires you to first provision the infrastructure that will be used to run your containers, what we call “infrastructure-first” development. As serverless technologies such as AWS Fargate become more popular, the need to provision infrastructure often goes away entirely, allowing customers to focus on their applications first. In this session, we discuss how a new concept in Amazon ECS called Capacity Providers enables application-first design and development of containerized applications, whether on Amazon EC2 or AWS Fargate.

[IhsanMujdeci]

Wow, thanks. Capacity providers boggled me becuase I assumed it worked "application first" style out of the box. It seems that it is a way for ECS to be aware of ASG and to spin up compute based on tasks or services instead of spinning up EC2 machines on ECS then putting tasks onto them.

[hopewise]

I could not find Task Placement option in Update Service steps

[Toramt]

32:32 One of the tenets of Spot is being AZ flexible; sounds like this would make spot less useful.