Learn more about AWS at - amzn.to/2LoB4PB. AWS London Summit 2018 - Breakout Session: A look at running containers in AWS Fargate without managing infrastructure.
I notice that the term "deep dive" is thrown around quite a bit these days but rarely is it accurate. The closest to "deep dives" that I have seen is when I have to deal with some nightmare outage and have to dig deep into the guts of some stack to solve the issues. I have at times been able to discuss very low layers with aws support/professional services to try and understand a given service from an architects viewpoint but difficult to get the low level details if its not documented in aws somewhere.. However, I will say that many could see this as a deep dive and I guess it depends on the audience .
She keeps talking about a decision on whether to run Fargate or ECS... that is confusing. From her slide that showed ECS vs EKS, on the ECS side it showed 2 different launch types, EC2 or Fargate. But the diagram showed that either one could be used WITH ECS. ECS being the orchestrator/control plane and EC2 or Fargate being the launch type. So why does she keep making it sound like ECS and Fargate are mutually exclusive? Is she sometimes saying "ECS" when she means EC2?
it is more of a comparison between aws kubernetes and fargate. But since it seems that fargate is an abstraction above kubernetes without using kubernetes but doing what kube does like kube does it. I guess this really is a 'deep dive.' Since there is not much to it XD
I'm new to AWS/ECS, I missed crucial explanation: what exactly is service and task? Why are these concepts separated? If I plan to run web inside container, is "task" proper name for it?
Task is a logical group of running containers. Service is the scheduling logic that decides when containers should run on a cluster. Cluster is a logical group of Amazon EC2 virtual machines. Refer to ua-cam.com/video/o_qSS4S1g34/v-deo.html
4:40 Abby - I respectfully disagree. The builder's application is the sandwich. Fargate is the 'global sandwich logistics chain' that abstracts away all the undifferentiated heavy lifting the builder wants the luxury of ignoring.
![AWS re:Invent 2019: [REPEAT 1] AWS Fargate under the hood (CON423-R1)](http://i.ytimg.com/vi/Hr-zOaBGyEA/mqdefault.jpg)
![AWS re:Invent 2018: [REPEAT] CI/CD for Serverless and Containerized Applications (DEV309-R)](/img/n.gif)
excellent talk @abbyfuller You packed so much information in 25 minutes
I notice that the term "deep dive" is thrown around quite a bit these days but rarely is it accurate. The closest to "deep dives" that I have seen is when I have to deal with some nightmare outage and have to dig deep into the guts of some stack to solve the issues. I have at times been able to discuss very low layers with aws support/professional services to try and understand a given service from an architects viewpoint but difficult to get the low level details if its not documented in aws somewhere.. However, I will say that many could see this as a deep dive and I guess it depends on the audience .
more like product intrduction rather than 'Dive deep'
I agree. This is NOT a Deep Dive at all. This is ~200 level.
She keeps talking about a decision on whether to run Fargate or ECS... that is confusing. From her slide that showed ECS vs EKS, on the ECS side it showed 2 different launch types, EC2 or Fargate. But the diagram showed that either one could be used WITH ECS. ECS being the orchestrator/control plane and EC2 or Fargate being the launch type. So why does she keep making it sound like ECS and Fargate are mutually exclusive? Is she sometimes saying "ECS" when she means EC2?
You can access to AWS fargate using ssh as long as you define in the docker image to install OpenSSH-server -- assign root host and password.
Great presentation. Very helpful.
Nice intro to Fargate. Not a deep dive...
good one.. she is good .. but not a deep dive at all... no demo
maybe you did not understand her because of her poor accent
it is more of a comparison between aws kubernetes and fargate. But since it seems that fargate is an abstraction above kubernetes without using kubernetes but doing what kube does like kube does it. I guess this really is a 'deep dive.' Since there is not much to it XD
Go @abbyfuller ! I always though we go EC2 first then do Fargate but what you said do Fargate first and shift to EC2 reserved/spot make sense now.
Thank you for this video. Your accent is music to my ears, and you rock!
I'm new to AWS/ECS, I missed crucial explanation: what exactly is service and task? Why are these concepts separated? If I plan to run web inside container, is "task" proper name for it?
Task is a logical group of running containers. Service is the scheduling logic that decides when containers should run on a cluster. Cluster is a logical group of Amazon EC2 virtual machines. Refer to ua-cam.com/video/o_qSS4S1g34/v-deo.html
ua-cam.com/video/wrZvlJlcZio/v-deo.html
4:40 Abby - I respectfully disagree. The builder's application is the sandwich. Fargate is the 'global sandwich logistics chain' that abstracts away all the undifferentiated heavy lifting the builder wants the luxury of ignoring.
I hope she noticed this
Deep Dive?
hmm "hoping for the best" if anyone is actually running business like this well good luck.
More like fartgate am I right
shez showing how much she knows...unfortunately not able to articulate any concepts or practices..