Skip to content

Unable to set service as DAEMON in cluster

0

Hi all, I'm trying to run a DAEMON service on an ECS cluster. I already tried and tested this on another newly created cluster. But when I try the same in quite an old cluster I get the following:

Service has unsupported scheduling strategy: DAEMON (Service: ApplicationAutoScaling, Status Code: 400)

Now, the capacity provider is default (which is none) for both clusters. I've seen in some forums that specifying launch_type = EC2 is a workaround, but I've already tried that to no avail.

What else could I try, or what could be the underlying issue here? I'm a bit at a loss given it worked on another cluster just fine.

asked 2 years ago884 views
1 Answer
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:

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html#service_scheduler_daemon

EXPERT
answered 2 years ago
EXPERT
reviewed 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!

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.