Announcing Accelerated Scale-Down of AWS Batch Managed Compute Environments
Amazon EC2 recently transitioned from hourly to per-second billing. Previously, as your jobs completed, AWS Batch would retain idle compute resources for the majority of the billing hour in order to avoid the cost associated with additional instance launches within the hour. With per-second billing, AWS customers are able to focus on their applications instead of maximizing usage to the hour. As a result, AWS Batch will now evaluate compute resources more frequently and immediately scale down any idle instances when there are no more runnable jobs in your job queues.
Amazon EC2 recently transitioned from hourly to per-second billing. Previously, as your jobs completed, AWS Batch would retain idle compute resources for the majority of the billing hour in order to avoid the cost associated with additional instance launches within the hour. With per-second billing, AWS customers are able to focus on their applications instead of maximizing usage to the hour. As a result, AWS Batch will now evaluate compute resources more frequently and immediately scale down any idle instances when there are no more runnable jobs in your job queues.
This change is effective today in the US East (Ohio), US West (Oregon), EU (Ireland), EU (London), EU (Frankfurt), Asia Pacific (Singapore), Asia Pacific (Tokyo), and Asia Pacific (Sydney) AWS Regions and will be effective in US East (N. Virginia) next week.
AWS Batch is currently available in the following regions:
- US East (N. Virginia) us-east-1
- US East (Ohio) us-east-2
- US West (Oregon) us-west-2
- EU (Ireland) eu-west-1
- EU (London) eu-west-2
- EU (Frankfurt) eu-central-1
- Asia Pacific (Tokyo) ap-northeast-1
- Asia Pacific (Singapore) ap-southeast-1
- Asia Pacific (Sydney) ap-southeast-2
For more information on AWS Batch: