News for hackers. Stuff that matters.
Re:AWS Fargate Deep Dive by bbgm on Saturday September 14, 2019 @10:38PM (#20975231)
One of the key things to remember about Fargate is the following.

Each Fargate task has its own isolation boundary and does not share the underlying kernel, CPU resources, memory resources, or elastic network interface with another task. (Source: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...)

The other part is patching. We are (I work at AWS) responsible for patching the underlying hosts. More details at https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...

Re:AWS Fargate Deep Dive by nnx on Saturday September 14, 2019 @11:26PM (#20975388)
> Each Fargate task has its own isolation boundary and does not share the underlying kernel, CPU resources, memory resources, or elastic network interface with another task.

Isn't Lambda the same as they're both using Firecracker under the hood isn't it?

Re:AWS Fargate Deep Dive by bbgm on Saturday September 14, 2019 @11:31PM (#20975406)
With or without Firecracker the isolation models are similar.
Re:AWS Fargate Deep Dive by dodobirdlord on Sunday September 15, 2019 @02:57AM (#20975962)
Yes