1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
Yes, you're correct. The Fargate service doesn't support Daemon scheduling strategy. You've to use EC2 as a launch type.
Did you specify EC2 as an launch type in both task definition and while creating a new ECS service?
When you use this strategy, you don't need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies.
Reference:
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago

Hi, thanks for the answer but the service isn't set in Fargate. As I mentioned previously, this worked just fine in a different cluster (dev) without even setting the EC2 as launch type explicitly so I'm wondering if there's something else. The describe cluster operation doesn't give me any out of the ordinary information.
Both the task and the service are set for EC2, so again, I'm not really sure what the problem could be. Are there any describe operations that could point me to the real issue?
Thank you again!