- 新しい順
- 投票が多い順
- コメントが多い順
Something that I would suggest is that you use AWS Fargate Spot for your lower environments; this will help you lower your cost up to 70% in your development environment by using spare compute capacity and you will be able to launch tasks based on your specified request. However, this is only recommended if you are able to sustain interruptions. Depending on your use case, this could be a great cost optimization strategy related to ECS Fargate.
Your only requirement is to add Fargate and Fargate_Spot as capacity providers when you create your cluster, and ensure that you are tracking your scaling either through scaling policies, step scaling policies or schedule scaling (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-auto-scaling.html)
You can also leverage the use of Compute Savings Plans, also available with Fargate to run your production environments. This combination of Savings Plans for Prod and SPOT compute capacity for development is a great strategy to help you cut down costs.
Monitoring:
You can use Cost Explorer in combination with tagging (Fargate resources such as task definitions, tasks, clusters and container instances). This will help you keep an eye on your spend and determine where you may need to focus to lower cost. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-account-settings.html#ecs-resource-ids
If you don't need the Dev or Staging environment for 24x7, you can write a Lambda function to stop and start the services on Fargate using Eventbridge to schedule the invocation of the Lambda function. That's what we did. It cut down our ECS bill a bit.
関連するコンテンツ
- 質問済み 3年前
AWS公式更新しました 2年前- AWS公式更新しました 4年前
Combination of Fargate and Fargate spot Capacity providers sounds promising. thank you for sharing detailed information.