UnmanagedComputeEnvironment
Unmanaged ComputeEnvironments do not provision or manage EC2 instances on your behalf.
Import
import { UnmanagedComputeEnvironment } from 'aws-cdk-lib/aws-batch';Or use the module namespace:
import * as batch from 'aws-cdk-lib/aws-batch';
// batch.UnmanagedComputeEnvironmentProperties
Configuration passed to the constructor as UnmanagedComputeEnvironmentProps.
unmanagedvCpusOptionalnumberThe vCPUs this Compute Environment provides. Used only by the scheduler to schedule jobs in `Queue`s that use `FairshareSchedulingPolicy`s. **If this parameter is not provided on a fairshare queue, no capacity is reserved**; that is, the `FairshareSchedulingPolicy` is ignored.
Default: 0
3 properties inherited from ComputeEnvironmentProps
computeEnvironmentNameOptionalinherited from ComputeEnvironmentPropsstringThe name of the ComputeEnvironment.
Default: - generated by CloudFormation
enabledOptionalinherited from ComputeEnvironmentPropsbooleanWhether 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`.
Default: true
serviceRoleOptionalinherited from ComputeEnvironmentPropsIRoleThe 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
Learn AWS the Practical Way
Our bi-weekly newsletter teaches hands-on AWS fundamentals. No certification fluff - just practical knowledge.
Subscribe to NewsletterQuick Facts
aws-batch