4 ms·
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, CP
by bbgm 7y ago
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/AWS_Fargate.html 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/platform_versions.html https://docs.aws.amazon.com/AmazonECS/latest/developerguide/...
- nnx 7y ago> 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?
- bbgm 7y agoWith or without Firecracker the isolation models are similar.
- dodobirdlord 7y agoYes