Please vote on this issue by adding a đź‘Ť reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
I would like to enable daemon-type scheduling and placement constraints for services running on external instances through ECS-Anywhere
Which service(s) is this request for?
ECS-A
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I have customers who have expressed a need to use external/on-prem resources to host their services, but also have business case need for the service to run as a daemon process. Currently, there seems to be no mechanism to do this, as this scheduling strategy is not supported for external services. Additionally, placement constraints are not part of the schema for external task definitions, which could be leveraged for a facsimile of this paradigm.
Are you currently working around this issue?
I am currently unaware of any known workaround for this issue
Community Note
Tell us about your request I would like to enable daemon-type scheduling and placement constraints for services running on external instances through ECS-Anywhere
Which service(s) is this request for? ECS-A
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? I have customers who have expressed a need to use external/on-prem resources to host their services, but also have business case need for the service to run as a daemon process. Currently, there seems to be no mechanism to do this, as this scheduling strategy is not supported for external services. Additionally, placement constraints are not part of the schema for external task definitions, which could be leveraged for a facsimile of this paradigm.
Are you currently working around this issue? I am currently unaware of any known workaround for this issue
Additional context
Attachments