Open source schedulers for deploying and managing applications on Amazon ECS with greater control and placement capabilities.
Blox is an open-source project that provides schedulers optimized for running applications on Amazon ECS. It gives developers greater control over how applications are deployed, run, and scaled across ECS clusters, leveraging ECS's placement capabilities. The project is delivered as a managed service via the Amazon ECS Console, API, and CLIs.
Developers and DevOps engineers using Amazon ECS who need advanced scheduling capabilities beyond the default ECS scheduler, such as daemon scheduling or custom scheduling logic. It is also suitable for teams interested in open-source collaboration on ECS scheduler designs.
Developers choose Blox for its open-source, extensible framework that provides fine-grained control over ECS scheduling while integrating seamlessly with AWS managed services. Its unique selling point is offering daemon scheduling and future schedulers as open-source alternatives, built on AWS primitives for reliability and scalability.
Open source tools for building custom schedulers on Amazon ECS
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Designs and code are fully open source, enabling community contributions and transparency, as highlighted in the README.
Delivered as a managed service via the Amazon ECS Console, API, and CLIs, ensuring seamless integration with AWS ecosystem.
Provides daemon scheduling capabilities for ECS, addressing a gap in the default scheduler for tasks that need to run on every node.
Framework is structured to allow addition of more schedulers beyond daemon, supporting future customization and scalability.
Deployment requires multiple steps: setting up IAM users, configuring AWS CLI, creating S3 buckets, and using Gradle tasks, which adds operational overhead.
Only daemon scheduling is available in v1.0; other schedulers are planned but not yet implemented, which may not meet immediate diverse needs.
Necessitates broad IAM permissions (e.g., s3:*, lambda:*), posing security risks and requiring separate test accounts, as admitted in the README.