Hello again! I want to create a very rough price estimate based on the Prefect Setup described here (https://towardsdatascience.com/how-to-cut-your-aws-ecs-costs-with-fargate-spot-and-prefect-1a1ba5d2e2df) by @Anna Geller. I have not much experience with AWS, yet, which makes it difficult to estimate the price using the price estimator. We will only have a couple of batch jobs running a couple of times a day and the processing will take place exclusively on snowflake, so the prefect flows will only deligate work. Also we would probably use prefect cloud. I would guess that in the price calculator here https://calculator.aws/#/createCalculator/Fargate we could go with Linux OS, 2 tasks/pods running 2 hours on average with 2 vCPU allocated and 4GB memory (minimum) and 20GB of storage (minimum). 1. Do you agree? If not, why? I can not really believe that this would only cost $14 per month. 2. Do I need to calculate additional costs for the ECS tasks? If I understand correctly, these are included in the Fargate price estimation. I know that we could save money by using spot instances. My target is to make a pessimistic/conservative price estimation. Thanks in advance! Really appreciate the help in this channel!

@André Petersen when it comes to Prefect Pricing, all plans include 20,000 free task runs each month, which is a lot to get started: https://www.prefect.io/pricing/ when it comes to AWS Pricing estimates, you would need to calculate separately the costs of: 1. The ECS service that runs Prefect agent 24/7 - this shouldn’t be too much since it’s only one ECS task, but still this one is always on. 2. The ECS tasks running your flows - this is where you can leverage both Fargate and spot instances if your budget is limited. You would need to estimate it based on how many flows you run and how long they run.

@Anna Geller Yes, so If I have only a few batch jobs per day, I would calculate 1 ECS service (which equals 1 task/pod in the fargate price estimation?) for the agent running 24/7 and 1 task for running the flows, which I would estimate to run 2 hours daily considering that processing in snowflake is fast. Does that make sense?

About the agent, that’s correct. Since you wanted a pessimistic/conservative price estimation, why not take say 20 ECS tasks running for 2 hours daily as an estimate?

Because we will have (in the beginning) 3 batch jobs that will probably run at most 30 minutes each and will probably be triggered once a day @Anna Geller

yeah, for the agent 1 vCPU (1024) and 2048 memory should be fine. For the tasks, it’s up to you, but you can use the same if your tasks don’t process any data in memory

Thanks @Anna Geller. Showing that this Fargate Service is probably even significantly cheaper than the MWAA AWS Service is good to know.