# IManagedEc2EcsComputeEnvironment

A ManagedComputeEnvironment that uses ECS orchestration on EC2 instances.

Extends: IManagedEc2EcsComputeEnvironment
Extends: IManagedComputeEnvironment
Implemented by: ManagedEc2EcsComputeEnvironment

- Source: [`aws-batch/lib/managed-compute-environment.ts`](https://github.com/aws/aws-cdk/blob/v2.275.0/packages/aws-cdk-lib/aws-batch/lib/managed-compute-environment.ts#L252)
- Type last changed: v2.249.0 · 13 Apr 2026

## Properties

- `allocationStrategy`: [AllocationStrategy](/cdk/api/v2/docs/aws-cdk-lib.aws_batch.AllocationStrategy.html) — The allocation strategy to use if not enough instances of the best fitting instance type can be allocated.

  **Default:** `BEST_FIT_PROGRESSIVE` if not using Spot instances, `SPOT_PRICE_CAPACITY_OPTIMIZED` if using Spot instances.

- `computeEnvironmentArn`: string — The ARN of this compute environment.

- `computeEnvironmentName`: string — The name of the ComputeEnvironment.

- `computeEnvironmentRef`: [ComputeEnvironmentReference](/cdk/api/v2/docs/aws-cdk-lib.interfaces.aws_batch.ComputeEnvironmentReference.html) — A reference to a ComputeEnvironment resource.

- `connections`: [Connections](/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.Connections.html) — The network connections associated with this resource.

- `enabled`: boolean — Whether or not this ComputeEnvironment can accept jobs from a Queue.

  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`.

- `env`: [ResourceEnvironment](/cdk/api/v2/docs/aws-cdk-lib.interfaces.ResourceEnvironment.html) — The environment this resource belongs to.

  For resources that are created and managed in a Stack (those created by
  creating new class instances like `new Role()`, `new Bucket()`, etc.), this
  is always the same as the environment of the stack they belong to.

  For referenced resources (those obtained from referencing methods like
  `Role.fromRoleArn()`, `Bucket.fromBucketName()`, etc.), they might be
  different than the stack they were imported into.

- `images`: [EcsMachineImage](/cdk/api/v2/docs/aws-cdk-lib.aws_batch.EcsMachineImage.html)[] — Configure which AMIs this Compute Environment can launch.

  **Default:** ECS_AL2 compatible AMI ids for non-GPU instances, ECS_AL2_NVIDIA compatible AMI ids for GPU instances. If the '@aws-cdk/aws-batch:defaultToAL2023' feature flag is set, ECS_AL2023 will be used instead of ECS_AL2.

  Leave this `undefined` to allow Batch to choose the latest AMIs it supports for each instance that it launches.

- `instanceClasses`: [InstanceClass](/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.InstanceClass.html)[] — The instance classes that this Compute Environment can launch.

  Which one is chosen depends on the `AllocationStrategy` used.
  Batch will automatically choose the size.

- `instanceRole`: [IRole](/cdk/api/v2/docs/aws-cdk-lib.aws_iam.IRole.html) — The execution Role that instances launched by this Compute Environment will use.

  **Default:** a role will be created

- `instanceTypes`: [InstanceType](/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.InstanceType.html)[] — The instance types that this Compute Environment can launch.

  Which one is chosen depends on the `AllocationStrategy` used.

- `launchTemplate`: [ILaunchTemplate](/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.ILaunchTemplate.html) — The Launch Template that this Compute Environment will use to provision EC2 Instances.

  **Default:** no launch template

  *Note*: if `securityGroups` is specified on both your
  launch template and this Compute Environment, **the
  `securityGroup`s on the Compute Environment override the
  ones on the launch template.

- `maxvCpus`: number — The maximum vCpus this `ManagedComputeEnvironment` can scale up to.

  *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`.

- `minvCpus`: number = 0 — The minimum vCPUs that an environment should maintain, even if the compute environment is DISABLED.

- `node`: [Node](/cdk/api/v2/docs/constructs.Node.html) — The tree node.

- `placementGroup`: [IPlacementGroup](/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.IPlacementGroup.html) — The EC2 placement group to associate with your compute resources.

  **Default:** no placement group

  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.

- `replaceComputeEnvironment`: boolean — Specifies whether this Compute Environment is replaced if an update is made that requires replacing its instances.

  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:

- `securityGroups`: [ISecurityGroup](/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.ISecurityGroup.html)[] — The security groups this Compute Environment will launch instances in.

- `serviceRole`: [IRole](/cdk/api/v2/docs/aws-cdk-lib.aws_iam.IRole.html) — The role Batch uses to perform actions on your behalf in your account, such as provision instances to run your jobs.

  **Default:** a serviceRole will be created for managed CEs, none for unmanaged CEs

- `spot`: boolean = false — Whether or not to use spot instances.

  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.

- `spotBidPercentage`: number = 100% — The maximum percentage that a Spot Instance price can be when compared with the On-Demand price for that instance type before instances are launched.

  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.

- `spotFleetRole`: [IRole](/cdk/api/v2/docs/aws-cdk-lib.aws_iam.IRole.html) — The service-linked role that Spot Fleet needs to launch instances on your behalf.

  **Default:** a new Role will be created

- `stack`: [Stack](/cdk/api/v2/docs/aws-cdk-lib.Stack.html) — The stack in which this resource is defined.

- `tags`: [TagManager](/cdk/api/v2/docs/aws-cdk-lib.TagManager.html) — TagManager to set, remove and format tags.

- `terminateOnUpdate`: boolean = false — Whether or not any running jobs will be immediately terminated when an infrastructure update occurs.

  If this is enabled, any terminated jobs may be retried, depending on the job's
  retry policy.

- `updateTimeout`: [Duration](/cdk/api/v2/docs/aws-cdk-lib.Duration.html) — Only meaningful if `terminateOnUpdate` is `false`.

  **Default:** 30 minutes

  If so,
  when an infrastructure update is triggered, any running jobs
  will be allowed to run until `updateTimeout` has expired.

- `updateToLatestImageVersion`: boolean = false — Whether or not the AMI is updated to the latest one supported by Batch when an infrastructure update occurs.

  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.

- `useOptimalInstanceClasses`: boolean = true — Whether or not to use batch's optimal instance type.

  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.

- `vpcSubnets`: [SubnetSelection](/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.SubnetSelection.html) — The VPC Subnets this Compute Environment will launch instances in.

## Methods

- `addInstanceClass(instanceClass: InstanceClass): void` — Add an instance class to this compute environment.

- `addInstanceType(instanceType: InstanceType): void` — Add an instance type to this compute environment.

- `applyRemovalPolicy(policy: RemovalPolicy): void` — Apply the given removal policy to this resource.

  The Removal Policy controls what happens to this resource when it stops
  being managed by CloudFormation, either because you've removed it from the
  CDK application or because you've made a change that requires the resource
  to be replaced.

  The resource can be deleted (`RemovalPolicy.DESTROY`), or left in your AWS
  account for data recovery and cleanup later (`RemovalPolicy.RETAIN`).

- `with(...mixins: IMixin[]): IConstruct` — Applies one or more mixins to this construct.

  Mixins are applied in order. The list of constructs is captured at the
  start of the call, so constructs added by a mixin will not be visited.

  **Parameters**

  - `mixins` — The mixins to apply.

  **Returns:** This construct for chaining