AWS Batch excels in scalability and parallelism, handling workloads from small to extensive. Users value the flexibility to customize compute and memory requirements. It integrates seamlessly with EC2, S3, Lambda, Step Functions, and supports Docker containers. Templates streamline configuration, while security features like IAM roles ensure controlled access. It's praised for cost-effectiveness, especially with Fargate, enhancing efficiency by eliminating dependencies on EC2 instances, and offering massive scaling with minimal setup.
- "AWS Batch is a cost-effective way to perform batch processing, primarily using spot instances and containers."
- "I appreciate that AWS Batch works with EC2, allowing me to launch jobs and automatically spin up the EC2 instance to run them, and when the jobs are completed, the EC2 instance shuts down, making it cost-effective."
- "The stability of AWS Batch is impeccable; we have run thousands of jobs without encountering any problems, and AWS Batch consistently performs as expected."
AWS Batch faces challenges with cost-effectiveness, documentation, UI glitches, and integration with other AWS services, causing difficulties for junior developers. Improved pricing, error handling for Spot Instances, cold start issues, and Fargate startup times are needed. Users suggest enhancements in deployment, logging, job monitoring, and IAM privilege setup. Faster log displays, advanced error handling, and better GUI descriptions would benefit technical and non-technical users. Scalability, reliability, and dynamic resource allocation require further development.
- "The user interface for queue searches could use fewer clicks, but that is a minor concern."
- "Setting up IAM privileges is cumbersome for me, as I am not a Cloud Engineer by training."
- "One main issue with AWS Batch is the startup time for Fargate, which takes 30 seconds, challenging for running quick jobs."