Interface ComputeResource.Builder
- All Superinterfaces:
Buildable
,CopyableBuilder<ComputeResource.Builder,
,ComputeResource> SdkBuilder<ComputeResource.Builder,
,ComputeResource> SdkPojo
- Enclosing class:
ComputeResource
-
Method Summary
Modifier and TypeMethodDescriptionallocationStrategy
(String allocationStrategy) The allocation strategy to use for the compute resource if not enough instances of the best fitting instance type can be allocated.allocationStrategy
(CRAllocationStrategy allocationStrategy) The allocation strategy to use for the compute resource if not enough instances of the best fitting instance type can be allocated.bidPercentage
(Integer bidPercentage) 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.desiredvCpus
(Integer desiredvCpus) The desired number of vCPUS in the compute environment.ec2Configuration
(Collection<Ec2Configuration> ec2Configuration) Provides information that's used to select Amazon Machine Images (AMIs) for Amazon EC2 instances in the compute environment.ec2Configuration
(Consumer<Ec2Configuration.Builder>... ec2Configuration) Provides information that's used to select Amazon Machine Images (AMIs) for Amazon EC2 instances in the compute environment.ec2Configuration
(Ec2Configuration... ec2Configuration) Provides information that's used to select Amazon Machine Images (AMIs) for Amazon EC2 instances in the compute environment.ec2KeyPair
(String ec2KeyPair) The Amazon EC2 key pair that's used for instances launched in the compute environment.Deprecated.This field is deprecated, use ec2Configuration[].imageIdOverride instead.instanceRole
(String instanceRole) The Amazon ECS instance profile applied to Amazon EC2 instances in a compute environment.instanceTypes
(String... instanceTypes) The instances types that can be launched.instanceTypes
(Collection<String> instanceTypes) The instances types that can be launched.default ComputeResource.Builder
launchTemplate
(Consumer<LaunchTemplateSpecification.Builder> launchTemplate) The launch template to use for your compute resources.launchTemplate
(LaunchTemplateSpecification launchTemplate) The launch template to use for your compute resources.The maximum number of vCPUs that a compute environment can support.The minimum number of vCPUs that a compute environment should maintain (even if the compute environment isDISABLED
).placementGroup
(String placementGroup) The Amazon EC2 placement group to associate with your compute resources.securityGroupIds
(String... securityGroupIds) The Amazon EC2 security groups that are associated with instances launched in the compute environment.securityGroupIds
(Collection<String> securityGroupIds) The Amazon EC2 security groups that are associated with instances launched in the compute environment.spotIamFleetRole
(String spotIamFleetRole) The Amazon Resource Name (ARN) of the Amazon EC2 Spot Fleet IAM role applied to aSPOT
compute environment.The VPC subnets where the compute resources are launched.subnets
(Collection<String> subnets) The VPC subnets where the compute resources are launched.Key-value pair tags to be applied to Amazon EC2 resources that are launched in the compute environment.The type of compute environment:EC2
,SPOT
,FARGATE
, orFARGATE_SPOT
.The type of compute environment:EC2
,SPOT
,FARGATE
, orFARGATE_SPOT
.Methods inherited from interface software.amazon.awssdk.utils.builder.CopyableBuilder
copy
Methods inherited from interface software.amazon.awssdk.utils.builder.SdkBuilder
applyMutation, build
Methods inherited from interface software.amazon.awssdk.core.SdkPojo
equalsBySdkFields, sdkFields
-
Method Details
-
type
The type of compute environment:
EC2
,SPOT
,FARGATE
, orFARGATE_SPOT
. For more information, see Compute environments in the Batch User Guide.If you choose
SPOT
, you must also specify an Amazon EC2 Spot Fleet role with thespotIamFleetRole
parameter. For more information, see Amazon EC2 spot fleet role in the Batch User Guide.- Parameters:
type
- The type of compute environment:EC2
,SPOT
,FARGATE
, orFARGATE_SPOT
. For more information, see Compute environments in the Batch User Guide.If you choose
SPOT
, you must also specify an Amazon EC2 Spot Fleet role with thespotIamFleetRole
parameter. For more information, see Amazon EC2 spot fleet role in the Batch User Guide.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
type
The type of compute environment:
EC2
,SPOT
,FARGATE
, orFARGATE_SPOT
. For more information, see Compute environments in the Batch User Guide.If you choose
SPOT
, you must also specify an Amazon EC2 Spot Fleet role with thespotIamFleetRole
parameter. For more information, see Amazon EC2 spot fleet role in the Batch User Guide.- Parameters:
type
- The type of compute environment:EC2
,SPOT
,FARGATE
, orFARGATE_SPOT
. For more information, see Compute environments in the Batch User Guide.If you choose
SPOT
, you must also specify an Amazon EC2 Spot Fleet role with thespotIamFleetRole
parameter. For more information, see Amazon EC2 spot fleet role in the Batch User Guide.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
allocationStrategy
The allocation strategy to use for the compute resource if not enough instances of the best fitting instance type can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more information, see Allocation strategies in the Batch User Guide.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- BEST_FIT (default)
-
Batch selects an instance type that best fits the needs of the jobs with a preference for the lowest-cost instance type. If additional instances of the selected instance type aren't available, Batch waits for the additional instances to be available. If there aren't enough instances available or the user is reaching Amazon EC2 service limits, additional jobs aren't run until the currently running jobs are completed. This allocation strategy keeps costs lower but can limit scaling. If you're using Spot Fleets with
BEST_FIT
, the Spot Fleet IAM Role must be specified. Compute resources that use aBEST_FIT
allocation strategy don't support infrastructure updates and can't update some parameters. For more information, see Updating compute environments in the Batch User Guide. - BEST_FIT_PROGRESSIVE
-
Batch selects additional instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types with lower cost vCPUs. If additional instances of the previously selected instance types aren't available, Batch selects new instance types.
- SPOT_CAPACITY_OPTIMIZED
-
Batch selects one or more instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types that are less likely to be interrupted. This allocation strategy is only available for Spot Instance compute resources.
- SPOT_PRICE_CAPACITY_OPTIMIZED
-
The price and capacity optimized allocation strategy looks at both price and capacity to select the Spot Instance pools that are the least likely to be interrupted and have the lowest possible price. This allocation strategy is only available for Spot Instance compute resources.
With
BEST_FIT_PROGRESSIVE
,SPOT_CAPACITY_OPTIMIZED
andSPOT_PRICE_CAPACITY_OPTIMIZED
(recommended) strategies using On-Demand or Spot Instances, and theBEST_FIT
strategy using Spot Instances, Batch might need to exceedmaxvCpus
to meet your capacity requirements. In this event, Batch never exceedsmaxvCpus
by more than a single instance.- Parameters:
allocationStrategy
- The allocation strategy to use for the compute resource if not enough instances of the best fitting instance type can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more information, see Allocation strategies in the Batch User Guide.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- BEST_FIT (default)
-
Batch selects an instance type that best fits the needs of the jobs with a preference for the lowest-cost instance type. If additional instances of the selected instance type aren't available, Batch waits for the additional instances to be available. If there aren't enough instances available or the user is reaching Amazon EC2 service limits, additional jobs aren't run until the currently running jobs are completed. This allocation strategy keeps costs lower but can limit scaling. If you're using Spot Fleets with
BEST_FIT
, the Spot Fleet IAM Role must be specified. Compute resources that use aBEST_FIT
allocation strategy don't support infrastructure updates and can't update some parameters. For more information, see Updating compute environments in the Batch User Guide. - BEST_FIT_PROGRESSIVE
-
Batch selects additional instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types with lower cost vCPUs. If additional instances of the previously selected instance types aren't available, Batch selects new instance types.
- SPOT_CAPACITY_OPTIMIZED
-
Batch selects one or more instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types that are less likely to be interrupted. This allocation strategy is only available for Spot Instance compute resources.
- SPOT_PRICE_CAPACITY_OPTIMIZED
-
The price and capacity optimized allocation strategy looks at both price and capacity to select the Spot Instance pools that are the least likely to be interrupted and have the lowest possible price. This allocation strategy is only available for Spot Instance compute resources.
With
BEST_FIT_PROGRESSIVE
,SPOT_CAPACITY_OPTIMIZED
andSPOT_PRICE_CAPACITY_OPTIMIZED
(recommended) strategies using On-Demand or Spot Instances, and theBEST_FIT
strategy using Spot Instances, Batch might need to exceedmaxvCpus
to meet your capacity requirements. In this event, Batch never exceedsmaxvCpus
by more than a single instance.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
allocationStrategy
The allocation strategy to use for the compute resource if not enough instances of the best fitting instance type can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more information, see Allocation strategies in the Batch User Guide.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- BEST_FIT (default)
-
Batch selects an instance type that best fits the needs of the jobs with a preference for the lowest-cost instance type. If additional instances of the selected instance type aren't available, Batch waits for the additional instances to be available. If there aren't enough instances available or the user is reaching Amazon EC2 service limits, additional jobs aren't run until the currently running jobs are completed. This allocation strategy keeps costs lower but can limit scaling. If you're using Spot Fleets with
BEST_FIT
, the Spot Fleet IAM Role must be specified. Compute resources that use aBEST_FIT
allocation strategy don't support infrastructure updates and can't update some parameters. For more information, see Updating compute environments in the Batch User Guide. - BEST_FIT_PROGRESSIVE
-
Batch selects additional instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types with lower cost vCPUs. If additional instances of the previously selected instance types aren't available, Batch selects new instance types.
- SPOT_CAPACITY_OPTIMIZED
-
Batch selects one or more instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types that are less likely to be interrupted. This allocation strategy is only available for Spot Instance compute resources.
- SPOT_PRICE_CAPACITY_OPTIMIZED
-
The price and capacity optimized allocation strategy looks at both price and capacity to select the Spot Instance pools that are the least likely to be interrupted and have the lowest possible price. This allocation strategy is only available for Spot Instance compute resources.
With
BEST_FIT_PROGRESSIVE
,SPOT_CAPACITY_OPTIMIZED
andSPOT_PRICE_CAPACITY_OPTIMIZED
(recommended) strategies using On-Demand or Spot Instances, and theBEST_FIT
strategy using Spot Instances, Batch might need to exceedmaxvCpus
to meet your capacity requirements. In this event, Batch never exceedsmaxvCpus
by more than a single instance.- Parameters:
allocationStrategy
- The allocation strategy to use for the compute resource if not enough instances of the best fitting instance type can be allocated. This might be because of availability of the instance type in the Region or Amazon EC2 service limits. For more information, see Allocation strategies in the Batch User Guide.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- BEST_FIT (default)
-
Batch selects an instance type that best fits the needs of the jobs with a preference for the lowest-cost instance type. If additional instances of the selected instance type aren't available, Batch waits for the additional instances to be available. If there aren't enough instances available or the user is reaching Amazon EC2 service limits, additional jobs aren't run until the currently running jobs are completed. This allocation strategy keeps costs lower but can limit scaling. If you're using Spot Fleets with
BEST_FIT
, the Spot Fleet IAM Role must be specified. Compute resources that use aBEST_FIT
allocation strategy don't support infrastructure updates and can't update some parameters. For more information, see Updating compute environments in the Batch User Guide. - BEST_FIT_PROGRESSIVE
-
Batch selects additional instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types with lower cost vCPUs. If additional instances of the previously selected instance types aren't available, Batch selects new instance types.
- SPOT_CAPACITY_OPTIMIZED
-
Batch selects one or more instance types that are large enough to meet the requirements of the jobs in the queue. Its preference is for instance types that are less likely to be interrupted. This allocation strategy is only available for Spot Instance compute resources.
- SPOT_PRICE_CAPACITY_OPTIMIZED
-
The price and capacity optimized allocation strategy looks at both price and capacity to select the Spot Instance pools that are the least likely to be interrupted and have the lowest possible price. This allocation strategy is only available for Spot Instance compute resources.
With
BEST_FIT_PROGRESSIVE
,SPOT_CAPACITY_OPTIMIZED
andSPOT_PRICE_CAPACITY_OPTIMIZED
(recommended) strategies using On-Demand or Spot Instances, and theBEST_FIT
strategy using Spot Instances, Batch might need to exceedmaxvCpus
to meet your capacity requirements. In this event, Batch never exceedsmaxvCpus
by more than a single instance.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
minvCpus
The minimum number of vCPUs that a compute environment should maintain (even if the compute environment is
DISABLED
).This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
minvCpus
- The minimum number of vCPUs that a compute environment should maintain (even if the compute environment isDISABLED
).This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
maxvCpus
The maximum number of vCPUs that a compute environment can support.
With
BEST_FIT_PROGRESSIVE
,SPOT_CAPACITY_OPTIMIZED
andSPOT_PRICE_CAPACITY_OPTIMIZED
(recommended) strategies using On-Demand or Spot Instances, and theBEST_FIT
strategy using Spot Instances, Batch might need to exceedmaxvCpus
to meet your capacity requirements. In this event, Batch never exceedsmaxvCpus
by more than a single instance.- Parameters:
maxvCpus
- The maximum number of vCPUs that a compute environment can support.With
BEST_FIT_PROGRESSIVE
,SPOT_CAPACITY_OPTIMIZED
andSPOT_PRICE_CAPACITY_OPTIMIZED
(recommended) strategies using On-Demand or Spot Instances, and theBEST_FIT
strategy using Spot Instances, Batch might need to exceedmaxvCpus
to meet your capacity requirements. In this event, Batch never exceedsmaxvCpus
by more than a single instance.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
desiredvCpus
The desired number of vCPUS in the compute environment. Batch modifies this value between the minimum and maximum values based on job queue demand.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
desiredvCpus
- The desired number of vCPUS in the compute environment. Batch modifies this value between the minimum and maximum values based on job queue demand.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
instanceTypes
The instances types that can be launched. You can specify instance families to launch any instance type within those families (for example,
c5
orp3
), or you can specify specific sizes within a family (such asc5.8xlarge
). You can also chooseoptimal
to select instance types (from the C4, M4, and R4 instance families) that match the demand of your job queues.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
When you create a compute environment, the instance types that you select for the compute environment must share the same architecture. For example, you can't mix x86 and ARM instances in the same compute environment.
Currently,
optimal
uses instance types from the C4, M4, and R4 instance families. In Regions that don't have instance types from those instance families, instance types from the C5, M5, and R5 instance families are used.- Parameters:
instanceTypes
- The instances types that can be launched. You can specify instance families to launch any instance type within those families (for example,c5
orp3
), or you can specify specific sizes within a family (such asc5.8xlarge
). You can also chooseoptimal
to select instance types (from the C4, M4, and R4 instance families) that match the demand of your job queues.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
When you create a compute environment, the instance types that you select for the compute environment must share the same architecture. For example, you can't mix x86 and ARM instances in the same compute environment.
Currently,
optimal
uses instance types from the C4, M4, and R4 instance families. In Regions that don't have instance types from those instance families, instance types from the C5, M5, and R5 instance families are used.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
instanceTypes
The instances types that can be launched. You can specify instance families to launch any instance type within those families (for example,
c5
orp3
), or you can specify specific sizes within a family (such asc5.8xlarge
). You can also chooseoptimal
to select instance types (from the C4, M4, and R4 instance families) that match the demand of your job queues.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
When you create a compute environment, the instance types that you select for the compute environment must share the same architecture. For example, you can't mix x86 and ARM instances in the same compute environment.
Currently,
optimal
uses instance types from the C4, M4, and R4 instance families. In Regions that don't have instance types from those instance families, instance types from the C5, M5, and R5 instance families are used.- Parameters:
instanceTypes
- The instances types that can be launched. You can specify instance families to launch any instance type within those families (for example,c5
orp3
), or you can specify specific sizes within a family (such asc5.8xlarge
). You can also chooseoptimal
to select instance types (from the C4, M4, and R4 instance families) that match the demand of your job queues.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
When you create a compute environment, the instance types that you select for the compute environment must share the same architecture. For example, you can't mix x86 and ARM instances in the same compute environment.
Currently,
optimal
uses instance types from the C4, M4, and R4 instance families. In Regions that don't have instance types from those instance families, instance types from the C5, M5, and R5 instance families are used.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
imageId
Deprecated.This field is deprecated, use ec2Configuration[].imageIdOverride instead.The Amazon Machine Image (AMI) ID used for instances launched in the compute environment. This parameter is overridden by the
imageIdOverride
member of theEc2Configuration
structure.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
The AMI that you choose for a compute environment must match the architecture of the instance types that you intend to use for that compute environment. For example, if your compute environment uses A1 instance types, the compute resource AMI that you choose must support ARM instances. Amazon ECS vends both x86 and ARM versions of the Amazon ECS-optimized Amazon Linux 2 AMI. For more information, see Amazon ECS-optimized Amazon Linux 2 AMI in the Amazon Elastic Container Service Developer Guide.
- Parameters:
imageId
- The Amazon Machine Image (AMI) ID used for instances launched in the compute environment. This parameter is overridden by theimageIdOverride
member of theEc2Configuration
structure.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
The AMI that you choose for a compute environment must match the architecture of the instance types that you intend to use for that compute environment. For example, if your compute environment uses A1 instance types, the compute resource AMI that you choose must support ARM instances. Amazon ECS vends both x86 and ARM versions of the Amazon ECS-optimized Amazon Linux 2 AMI. For more information, see Amazon ECS-optimized Amazon Linux 2 AMI in the Amazon Elastic Container Service Developer Guide.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
subnets
The VPC subnets where the compute resources are launched. These subnets must be within the same VPC. Fargate compute resources can contain up to 16 subnets. For more information, see VPCs and subnets in the Amazon VPC User Guide.
Batch on Amazon EC2 and Batch on Amazon EKS support Local Zones. For more information, see Local Zones in the Amazon EC2 User Guide for Linux Instances, Amazon EKS and Amazon Web Services Local Zones in the Amazon EKS User Guide and Amazon ECS clusters in Local Zones, Wavelength Zones, and Amazon Web Services Outposts in the Amazon ECS Developer Guide.
Batch on Fargate doesn't currently support Local Zones.
- Parameters:
subnets
- The VPC subnets where the compute resources are launched. These subnets must be within the same VPC. Fargate compute resources can contain up to 16 subnets. For more information, see VPCs and subnets in the Amazon VPC User Guide.Batch on Amazon EC2 and Batch on Amazon EKS support Local Zones. For more information, see Local Zones in the Amazon EC2 User Guide for Linux Instances, Amazon EKS and Amazon Web Services Local Zones in the Amazon EKS User Guide and Amazon ECS clusters in Local Zones, Wavelength Zones, and Amazon Web Services Outposts in the Amazon ECS Developer Guide.
Batch on Fargate doesn't currently support Local Zones.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
subnets
The VPC subnets where the compute resources are launched. These subnets must be within the same VPC. Fargate compute resources can contain up to 16 subnets. For more information, see VPCs and subnets in the Amazon VPC User Guide.
Batch on Amazon EC2 and Batch on Amazon EKS support Local Zones. For more information, see Local Zones in the Amazon EC2 User Guide for Linux Instances, Amazon EKS and Amazon Web Services Local Zones in the Amazon EKS User Guide and Amazon ECS clusters in Local Zones, Wavelength Zones, and Amazon Web Services Outposts in the Amazon ECS Developer Guide.
Batch on Fargate doesn't currently support Local Zones.
- Parameters:
subnets
- The VPC subnets where the compute resources are launched. These subnets must be within the same VPC. Fargate compute resources can contain up to 16 subnets. For more information, see VPCs and subnets in the Amazon VPC User Guide.Batch on Amazon EC2 and Batch on Amazon EKS support Local Zones. For more information, see Local Zones in the Amazon EC2 User Guide for Linux Instances, Amazon EKS and Amazon Web Services Local Zones in the Amazon EKS User Guide and Amazon ECS clusters in Local Zones, Wavelength Zones, and Amazon Web Services Outposts in the Amazon ECS Developer Guide.
Batch on Fargate doesn't currently support Local Zones.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
securityGroupIds
The Amazon EC2 security groups that are associated with instances launched in the compute environment. One or more security groups must be specified, either in
securityGroupIds
or using a launch template referenced inlaunchTemplate
. This parameter is required for jobs that are running on Fargate resources and must contain at least one security group. Fargate doesn't support launch templates. If security groups are specified using bothsecurityGroupIds
andlaunchTemplate
, the values insecurityGroupIds
are used.- Parameters:
securityGroupIds
- The Amazon EC2 security groups that are associated with instances launched in the compute environment. One or more security groups must be specified, either insecurityGroupIds
or using a launch template referenced inlaunchTemplate
. This parameter is required for jobs that are running on Fargate resources and must contain at least one security group. Fargate doesn't support launch templates. If security groups are specified using bothsecurityGroupIds
andlaunchTemplate
, the values insecurityGroupIds
are used.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
securityGroupIds
The Amazon EC2 security groups that are associated with instances launched in the compute environment. One or more security groups must be specified, either in
securityGroupIds
or using a launch template referenced inlaunchTemplate
. This parameter is required for jobs that are running on Fargate resources and must contain at least one security group. Fargate doesn't support launch templates. If security groups are specified using bothsecurityGroupIds
andlaunchTemplate
, the values insecurityGroupIds
are used.- Parameters:
securityGroupIds
- The Amazon EC2 security groups that are associated with instances launched in the compute environment. One or more security groups must be specified, either insecurityGroupIds
or using a launch template referenced inlaunchTemplate
. This parameter is required for jobs that are running on Fargate resources and must contain at least one security group. Fargate doesn't support launch templates. If security groups are specified using bothsecurityGroupIds
andlaunchTemplate
, the values insecurityGroupIds
are used.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
ec2KeyPair
The Amazon EC2 key pair that's used for instances launched in the compute environment. You can use this key pair to log in to your instances with SSH.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
ec2KeyPair
- The Amazon EC2 key pair that's used for instances launched in the compute environment. You can use this key pair to log in to your instances with SSH.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
instanceRole
The Amazon ECS instance profile applied to Amazon EC2 instances in a compute environment. This parameter is required for Amazon EC2 instances types. You can specify the short name or full Amazon Resource Name (ARN) of an instance profile. For example,
ecsInstanceRole
orarn:aws:iam::<aws_account_id>:instance-profile/ecsInstanceRole
. For more information, see Amazon ECS instance role in the Batch User Guide.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
instanceRole
- The Amazon ECS instance profile applied to Amazon EC2 instances in a compute environment. This parameter is required for Amazon EC2 instances types. You can specify the short name or full Amazon Resource Name (ARN) of an instance profile. For example,ecsInstanceRole
orarn:aws:iam::<aws_account_id>:instance-profile/ecsInstanceRole
. For more information, see Amazon ECS instance role in the Batch User Guide.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
tags
Key-value pair tags to be applied to Amazon EC2 resources that are launched in the compute environment. For Batch, these take the form of
"String1": "String2"
, whereString1
is the tag key andString2
is the tag value-for example,{ "Name": "Batch Instance - C4OnDemand" }
. This is helpful for recognizing your Batch instances in the Amazon EC2 console. Updating these tags requires an infrastructure update to the compute environment. For more information, see Updating compute environments in the Batch User Guide. These tags aren't seen when using the BatchListTagsForResource
API operation.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
tags
- Key-value pair tags to be applied to Amazon EC2 resources that are launched in the compute environment. For Batch, these take the form of"String1": "String2"
, whereString1
is the tag key andString2
is the tag value-for example,{ "Name": "Batch Instance - C4OnDemand" }
. This is helpful for recognizing your Batch instances in the Amazon EC2 console. Updating these tags requires an infrastructure update to the compute environment. For more information, see Updating compute environments in the Batch User Guide. These tags aren't seen when using the BatchListTagsForResource
API operation.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
placementGroup
The Amazon EC2 placement group to associate with your compute resources. If you intend to submit multi-node parallel jobs to your 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. For more information, see Placement groups in the Amazon EC2 User Guide for Linux Instances.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
placementGroup
- The Amazon EC2 placement group to associate with your compute resources. If you intend to submit multi-node parallel jobs to your 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. For more information, see Placement groups in the Amazon EC2 User Guide for Linux Instances.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
bidPercentage
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%, then the Spot price must be less than 20% of the current On-Demand price for that Amazon EC2 instance. You always pay the lowest (market) price and never more than your maximum percentage. If you leave this field empty, the default value is 100% of the On-Demand price. For most use cases, we recommend leaving this field empty.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
bidPercentage
- 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%, then the Spot price must be less than 20% of the current On-Demand price for that Amazon EC2 instance. You always pay the lowest (market) price and never more than your maximum percentage. If you leave this field empty, the default value is 100% of the On-Demand price. For most use cases, we recommend leaving this field empty.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
spotIamFleetRole
The Amazon Resource Name (ARN) of the Amazon EC2 Spot Fleet IAM role applied to a
SPOT
compute environment. This role is required if the allocation strategy set toBEST_FIT
or if the allocation strategy isn't specified. For more information, see Amazon EC2 spot fleet role in the Batch User Guide.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
To tag your Spot Instances on creation, the Spot Fleet IAM role specified here must use the newer AmazonEC2SpotFleetTaggingRole managed policy. The previously recommended AmazonEC2SpotFleetRole managed policy doesn't have the required permissions to tag Spot Instances. For more information, see Spot instances not tagged on creation in the Batch User Guide.
- Parameters:
spotIamFleetRole
- The Amazon Resource Name (ARN) of the Amazon EC2 Spot Fleet IAM role applied to aSPOT
compute environment. This role is required if the allocation strategy set toBEST_FIT
or if the allocation strategy isn't specified. For more information, see Amazon EC2 spot fleet role in the Batch User Guide.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
To tag your Spot Instances on creation, the Spot Fleet IAM role specified here must use the newer AmazonEC2SpotFleetTaggingRole managed policy. The previously recommended AmazonEC2SpotFleetRole managed policy doesn't have the required permissions to tag Spot Instances. For more information, see Spot instances not tagged on creation in the Batch User Guide.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
launchTemplate
The launch template to use for your compute resources. Any other compute resource parameters that you specify in a CreateComputeEnvironment API operation override the same parameters in the launch template. You must specify either the launch template ID or launch template name in the request, but not both. For more information, see Launch template support in the Batch User Guide.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
launchTemplate
- The launch template to use for your compute resources. Any other compute resource parameters that you specify in a CreateComputeEnvironment API operation override the same parameters in the launch template. You must specify either the launch template ID or launch template name in the request, but not both. For more information, see Launch template support in the Batch User Guide.This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
launchTemplate
default ComputeResource.Builder launchTemplate(Consumer<LaunchTemplateSpecification.Builder> launchTemplate) The launch template to use for your compute resources. Any other compute resource parameters that you specify in a CreateComputeEnvironment API operation override the same parameters in the launch template. You must specify either the launch template ID or launch template name in the request, but not both. For more information, see Launch template support in the Batch User Guide.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
LaunchTemplateSpecification.Builder
avoiding the need to create one manually viaLaunchTemplateSpecification.builder()
.When the
Consumer
completes,SdkBuilder.build()
is called immediately and its result is passed tolaunchTemplate(LaunchTemplateSpecification)
.- Parameters:
launchTemplate
- a consumer that will call methods onLaunchTemplateSpecification.Builder
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
ec2Configuration
Provides information that's used to select Amazon Machine Images (AMIs) for Amazon EC2 instances in the compute environment. If
Ec2Configuration
isn't specified, the default isECS_AL2
.One or two values can be provided.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
ec2Configuration
- Provides information that's used to select Amazon Machine Images (AMIs) for Amazon EC2 instances in the compute environment. IfEc2Configuration
isn't specified, the default isECS_AL2
.One or two values can be provided.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
ec2Configuration
Provides information that's used to select Amazon Machine Images (AMIs) for Amazon EC2 instances in the compute environment. If
Ec2Configuration
isn't specified, the default isECS_AL2
.One or two values can be provided.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Parameters:
ec2Configuration
- Provides information that's used to select Amazon Machine Images (AMIs) for Amazon EC2 instances in the compute environment. IfEc2Configuration
isn't specified, the default isECS_AL2
.One or two values can be provided.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
ec2Configuration
Provides information that's used to select Amazon Machine Images (AMIs) for Amazon EC2 instances in the compute environment. If
Ec2Configuration
isn't specified, the default isECS_AL2
.One or two values can be provided.
This parameter isn't applicable to jobs that are running on Fargate resources. Don't specify it.
Ec2Configuration.Builder
avoiding the need to create one manually viaEc2Configuration.builder()
.When the
Consumer
completes,SdkBuilder.build()
is called immediately and its result is passed toec2Configuration(List<Ec2Configuration>)
.- Parameters:
ec2Configuration
- a consumer that will call methods onEc2Configuration.Builder
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-