ManagedEc2EcsComputeEnvironmentProps Struct
Props for a ManagedEc2EcsComputeEnvironment.
Example
declare const vpc: ec2.IVpc;
const computeEnv = new batch.ManagedEc2EcsComputeEnvironment(this, 'Ec2ComputeEnv', {
vpc,
instanceTypes: [ec2.InstanceType.of(ec2.InstanceClass.M5AD, ec2.InstanceSize.LARGE)],
// useOptimalInstanceClasses: true (default)
});
// Result: ['m5ad.large', 'optimal']
Properties
allocationStrategyAllocationStrategyallocation_strategyAllocationStrategyallocationStrategyAllocationStrategyAllocationStrategyAllocationStrategyAllocationStrategyAllocationStrategy= `BEST_FIT_PROGRESSIVE` if not us…#default
Default: BEST_FIT_PROGRESSIVE if not using Spot instances, SPOT_PRICE_CAPACITY_OPTIMIZED if using Spot instances.
computeEnvironmentNamestringcompute_environment_namestrcomputeEnvironmentNameStringComputeEnvironmentNamestringComputeEnvironmentName*string= generated by CloudFormation#defaultInstanceClassesDefaultInstanceClass[]default_instance_classestyping.List[DefaultInstanceClass]defaultInstanceClassesList<DefaultInstanceClass>DefaultInstanceClassesDefaultInstanceClass[]DefaultInstanceClasses*[]DefaultInstanceClass= choose from instanceTypes and in…#A simpler way to choose up-to-date instance classes based on region instead of specifying exact instance classes.
default
Default: choose from instanceTypes and instanceClasses
notes
Enabled ComputeEnvironments can accept jobs from a Queue and can scale instances up or down. Disabled ComputeEnvironments cannot accept jobs from a Queue or scale instances up or down.
If you change a ComputeEnvironment from enabled to disabled while it is executing jobs, Jobs in the STARTED or RUNNING states will not be interrupted. As jobs complete, the ComputeEnvironment will scale instances down to minvCpus.
To ensure you aren't billed for unused capacity, set minvCpus to 0.
imagesEcsMachineImage[]imagestyping.List[EcsMachineImage]imagesList<EcsMachineImage>ImagesEcsMachineImage[]Images*[]EcsMachineImage= ECS_AL2 for non-GPU instances, E…#notes · default
If you specify this property with only image specified, then the imageType will default to ECS_AL2 (or ECS_AL2023 if the @aws-cdk/aws-batch:defaultToAL2023 feature flag is set). If your image needs GPU resources, specify ECS_AL2_NVIDIA or ECS_AL2023_NVIDIA; otherwise, the instances will not be able to properly join the ComputeEnvironment.
Default: ECS_AL2 for non-GPU instances, ECS_AL2_NVIDIA for GPU instances. If the '@aws-cdk/aws-batch:defaultToAL2023' feature flag is set, ECS_AL2023 will be used instead of ECS_AL2.
instanceClassesInstanceClass[]instance_classestyping.List[InstanceClass]instanceClassesList<InstanceClass>InstanceClassesInstanceClass[]InstanceClasses*[]InstanceClass= the instances Batch considers wi…#Which one is chosen depends on the AllocationStrategy used. Batch will automatically choose the instance size.
default
Default: the instances Batch considers will be used (currently C4, M4, and R4)
instanceRoleIRoleinstance_roleIRoleinstanceRoleIRoleInstanceRoleIRoleInstanceRoleIRole= a role will be created#instanceTypesInstanceType[]instance_typestyping.List[InstanceType]instanceTypesList<InstanceType>InstanceTypesInstanceType[]InstanceTypes*[]InstanceType= the instances Batch considers wi…#Which one is chosen depends on the AllocationStrategy used.
default
Default: the instances Batch considers will be used (currently C4, M4, and R4)
launchTemplateILaunchTemplatelaunch_templateILaunchTemplatelaunchTemplateILaunchTemplateLaunchTemplateILaunchTemplateLaunchTemplateILaunchTemplate= no launch template#Note: if securityGroups is specified on both your launch template and this Compute Environment, **the securityGroups on the Compute Environment override the ones on the launch template.
notes
Note: if this Compute Environment uses EC2 resources (not Fargate) with either AllocationStrategy.BEST_FIT_PROGRESSIVE or AllocationStrategy.SPOT_CAPACITY_OPTIMIZED, or AllocationStrategy.BEST_FIT with Spot instances, The scheduler may exceed this number by at most one of the instances specified in instanceTypes or instanceClasses.
placementGroupIPlacementGroupRefplacement_groupIPlacementGroupRefplacementGroupIPlacementGroupRefPlacementGroupIPlacementGroupRefPlacementGroupIPlacementGroupRef= no placement group#notes
If you intend to submit multi-node parallel jobs to this Compute Environment, you should consider creating a cluster placement group and associate it with your compute resources. This keeps your multi-node parallel job on a logical grouping of instances within a single Availability Zone with high network flow potential.
replaceComputeEnvironmentbooleanreplace_compute_environmentboolreplaceComputeEnvironmentBooleanReplaceComputeEnvironmentboolReplaceComputeEnvironment*bool= false#notes
To enable more properties to be updated, set this property to false. When changing the value of this property to false, do not change any other properties at the same time. If other properties are changed at the same time, and the change needs to be rolled back but it can't, it's possible for the stack to go into the UPDATE_ROLLBACK_FAILED state. You can't update a stack that is in the UPDATE_ROLLBACK_FAILED state. However, if you can continue to roll it back, you can return the stack to its original settings and then try to update it again.
The properties which require a replacement of the Compute Environment are:
securityGroupsISecurityGroup[]security_groupstyping.List[ISecurityGroup]securityGroupsList<ISecurityGroup>SecurityGroupsISecurityGroup[]SecurityGroups*[]ISecurityGroup= new security groups will be crea…#default
Default: new security groups will be created
serviceRoleIRoleservice_roleIRoleserviceRoleIRoleServiceRoleIRoleServiceRoleIRole= a serviceRole will be created fo…#default
Default: a serviceRole will be created for managed CEs, none for unmanaged CEs
Spot instances are less expensive EC2 instances that can be reclaimed by EC2 at any time; your job will be given two minutes of notice before reclamation.
spotBidPercentagenumberspot_bid_percentageint | floatspotBidPercentageNumberSpotBidPercentagedoubleSpotBidPercentage*float64= 100%#notes
For example, if your maximum percentage is 20%, the Spot price must be less than 20% of the current On-Demand price for that Instance. You always pay the lowest market price and never more than your maximum percentage. For most use cases, Batch recommends leaving this field empty.
Implies spot == true if set
spotFleetRoleIRolespot_fleet_roleIRolespotFleetRoleIRoleSpotFleetRoleIRoleSpotFleetRoleIRole= a new role will be created#terminateOnUpdatebooleanterminate_on_updateboolterminateOnUpdateBooleanTerminateOnUpdateboolTerminateOnUpdate*bool= false#If this is enabled, any terminated jobs may be retried, depending on the job's retry policy.
updateTimeoutDurationupdate_timeoutDurationupdateTimeoutDurationUpdateTimeoutDurationUpdateTimeoutDuration= 30 minutes#If so, when an infrastructure update is triggered, any running jobs will be allowed to run until updateTimeout has expired.
updateToLatestImageVersionbooleanupdate_to_latest_image_versionboolupdateToLatestImageVersionBooleanUpdateToLatestImageVersionboolUpdateToLatestImageVersion*bool= false#If you specify a specific AMI, this property will be ignored.
Note: the CDK will never set this value by default, false will set by CFN. This is to avoid a deployment failure that occurs when this value is set.
useOptimalInstanceClassesbooleanuse_optimal_instance_classesbooluseOptimalInstanceClassesBooleanUseOptimalInstanceClassesboolUseOptimalInstanceClasses*bool= true#The optimal instance type is equivalent to adding the C4, M4, and R4 instance classes. You can specify other instance classes (of the same architecture) in addition to the optimal instance classes.
vpcSubnetsSubnetSelectionvpc_subnetsSubnetSelectionvpcSubnetsSubnetSelectionVpcSubnetsSubnetSelectionVpcSubnetsSubnetSelection= new subnets will be created#