Replies: 1 comment 2 replies
-
This is an interesting use-case, would not be possible to use ECS Anywhere along with Batch API? doing so you would not need to implement a custom executor for nextflow |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello.
My team has been running a Nextflow pipeline to crunch a lot of data. In the past we have had good experience with the tooling that your Nextflow provides, especially the integration with AWS Batch and S3. However, I think we have optimized the dollar costs per run as much as we can with AWS Batch (using EC2 spot) and S3, and it is still not good enough to meet our targets given the budget constraints.
Because of this, we are exploring the option to rent 3rd party or on-prem hardware and then orchestrate the containerized tasks using Amazon's ECS Anywhere feature. But I could not find any documentation on how to write our own executor/plugin for this use case. I am fairly confident that if we can run Nextflow on AWS Batch, we should be able to run it on ECS directly as well. At the same time, we do not have the bandwidth to run and maintain an EKS cluster to use the k8s executor (assuming its possible to do that).
Any help or pointers to relevant docs or source code would be appreciated.
Thanks for listening. We love Nextflow!
Beta Was this translation helpful? Give feedback.
All reactions