Skip to content

docs(batch): correct default allocation strategy for spot compute environments #36356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mergify merged 6 commits into from
Dec 19, 2025
+6 −6
Merged

docs(batch): correct default allocation strategy for spot compute environments #36356

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
b0deb86
docs(aws-batch): correct default allocation strategy for spot compute…
jasdeepbhalla Dec 11, 2025
7fefdbc
Merge branch 'main' into 36348_aws_batch_docs
kumsmrit Dec 16, 2025
a028076
Merge branch 'main' into 36348_aws_batch_docs
kumsmrit Dec 16, 2025
5f35f73
Merge branch 'main' into 36348_aws_batch_docs
kumsmrit Dec 17, 2025
2ec2eae
Merge branch 'main' into 36348_aws_batch_docs
kumsmrit Dec 18, 2025
d8db58d
Merge branch 'main' into 36348_aws_batch_docs
kumsmrit Dec 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions packages/aws-cdk-lib/aws-batch/lib/managed-compute-environment.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,7 @@ export interface IManagedEc2EcsComputeEnvironment extends IManagedComputeEnviron
* the best fitting instance type can be allocated.
*
* @default - `BEST_FIT_PROGRESSIVE` if not using Spot instances,
* `SPOT_CAPACITY_OPTIMIZED` if using Spot instances.
* `SPOT_PRICE_CAPACITY_OPTIMIZED` if using Spot instances.
*/
readonly allocationStrategy?: AllocationStrategy;

Expand Down Expand Up @@ -463,8 +463,8 @@ export enum AllocationStrategy {

/**
* If your workflow tolerates interruptions, you should enable `spot` on your `ComputeEnvironment`
* and use `SPOT_CAPACITY_OPTIMIZED` (this is the default if `spot` is enabled).
* This will tell Batch to choose the instance types from the ones you’ve specified that have
* and use `SPOT_CAPACITY_OPTIMIZED`.
* This will tell Batch to choose the instance types from the ones you've specified that have
* the most spot capacity available to minimize the chance of interruption.
* To get the most benefit from your spot instances,
* you should allow Batch to choose from as many different instance types as possible.
Expand Down Expand Up @@ -540,7 +540,7 @@ export interface ManagedEc2EcsComputeEnvironmentProps extends ManagedComputeEnvi
* the best fitting instance type can be allocated.
*
* @default - `BEST_FIT_PROGRESSIVE` if not using Spot instances,
* `SPOT_CAPACITY_OPTIMIZED` if using Spot instances.
* `SPOT_PRICE_CAPACITY_OPTIMIZED` if using Spot instances.
*/
readonly allocationStrategy?: AllocationStrategy;

Expand Down Expand Up @@ -815,7 +815,7 @@ interface IManagedEc2EksComputeEnvironment extends IManagedComputeEnvironment {
* the best fitting instance type can be allocated.
*
* @default - `BEST_FIT_PROGRESSIVE` if not using Spot instances,
* `SPOT_CAPACITY_OPTIMIZED` if using Spot instances.
* `SPOT_PRICE_CAPACITY_OPTIMIZED` if using Spot instances.
*/
readonly allocationStrategy?: AllocationStrategy;

Expand Down Expand Up @@ -957,7 +957,7 @@ export interface ManagedEc2EksComputeEnvironmentProps extends ManagedComputeEnvi
* the best fitting instance type can be allocated.
*
* @default - `BEST_FIT_PROGRESSIVE` if not using Spot instances,
* `SPOT_CAPACITY_OPTIMIZED` if using Spot instances.
* `SPOT_PRICE_CAPACITY_OPTIMIZED` if using Spot instances.
*/
readonly allocationStrategy?: AllocationStrategy;

Expand Down
Loading