AWS Batch now allows you to configure a scale down delay for managed compute environments, helping reduce job processing delays for intermittent and periodic workloads. With the new minScaleDownDelayMinutes parameter, you can specify how long AWS Batch keeps instances running after their jobs complete (from 20 minutes to 1 week), preventing unnecessary instance terminations and relaunches that can delay subsequent job processing.
You can configure the scale down delay when creating or updating a compute environment via the AWS Batch API (CreateComputeEnvironment or UpdateComputeEnvironment) or the AWS Batch Management Console. The delay is applied at the instance level, based on when each instance last completed a job.
Scale down delay is supported today in all AWS Regions where AWS Batch is available. For more information, see the AWS Batch API Guide.
Categories:
Source: Amazon Web Services
Latest Posts
- MC1450134: Microsoft Entra Recognizes Windows Hello for Business and macOS Platform SSO as Standalone MFA Factors
- MC1506982: Microsoft 365 Apps Gets October 2026 Updates for All Channels
- AWS Agent Registry now supports custom metadata for registry records
- Amazon Location Service launches an interactive API Playground featuring Places, Routes and Maps APIs
