- 최신
- 최다 투표
- 가장 많은 댓글
Hello Hermosa,
When using AWS Fargate, it’s important to note that it is designed to provide a serverless experience. As a part of the experience this means that AWS manages the underlying infrastructure, including the selection of instance types, on behalf of our customer. Unfortunately this also means that, direct control over specific instance types is not available with Fargate.
The reason is to maintain the serverless nature of AWS Fargate. AWS takes care of managing the underlying infrastructure allowing Fargate to scale automatically, so customers don't need to worry about selecting instance types or handling other infrastructure details.
If you are struggling between which choice to make, Fargate or EC2 launch types. I will advise you to look at your workload. If performance is critical (top priority) and you need control over the underlying instance types. I will suggest for you to go with the EC2 launch type instead of Fargate.
If you think my response answers your question please select it as the accepted answer cheers!
Hello.
Fargate is serverless, so there is no concept of instance types.
Performance is determined by the vCPU and memory values set in the task definition.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/AWS_Fargate.html
AWS Fargate is a technology that you can use with Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances. With AWS Fargate, you no longer have to provision, configure, or scale clusters of virtual machines to run containers. This removes the need to choose server types, decide when to scale your clusters, or optimize cluster packing.
CPU architecture can be set in the task definition.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-tasks-services.html#fargate-task-os
Hmm thanks for your response seems like we have to stick with EC2 launch type