@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class SpotOptionsRequest extends Object implements Serializable, Cloneable
Describes the configuration of Spot Instances in an EC2 Fleet request.
| Constructor and Description |
|---|
SpotOptionsRequest() |
| Modifier and Type | Method and Description |
|---|---|
SpotOptionsRequest |
clone() |
boolean |
equals(Object obj) |
String |
getAllocationStrategy()
The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance pools
specified by the EC2 Fleet launch configuration.
|
String |
getInstanceInterruptionBehavior()
The behavior when a Spot Instance is interrupted.
|
Integer |
getInstancePoolsToUseCount()
The number of Spot pools across which to allocate your target Spot capacity.
|
FleetSpotMaintenanceStrategiesRequest |
getMaintenanceStrategies()
The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
|
String |
getMaxTotalPrice()
The maximum amount per hour for Spot Instances that you're willing to pay.
|
Integer |
getMinTargetCapacity()
The minimum target capacity for Spot Instances in the fleet.
|
Boolean |
getSingleAvailabilityZone()
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
|
Boolean |
getSingleInstanceType()
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
|
int |
hashCode() |
Boolean |
isSingleAvailabilityZone()
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
|
Boolean |
isSingleInstanceType()
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
|
void |
setAllocationStrategy(String allocationStrategy)
The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance pools
specified by the EC2 Fleet launch configuration.
|
void |
setInstanceInterruptionBehavior(String instanceInterruptionBehavior)
The behavior when a Spot Instance is interrupted.
|
void |
setInstancePoolsToUseCount(Integer instancePoolsToUseCount)
The number of Spot pools across which to allocate your target Spot capacity.
|
void |
setMaintenanceStrategies(FleetSpotMaintenanceStrategiesRequest maintenanceStrategies)
The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
|
void |
setMaxTotalPrice(String maxTotalPrice)
The maximum amount per hour for Spot Instances that you're willing to pay.
|
void |
setMinTargetCapacity(Integer minTargetCapacity)
The minimum target capacity for Spot Instances in the fleet.
|
void |
setSingleAvailabilityZone(Boolean singleAvailabilityZone)
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
|
void |
setSingleInstanceType(Boolean singleInstanceType)
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
|
String |
toString()
Returns a string representation of this object.
|
SpotOptionsRequest |
withAllocationStrategy(SpotAllocationStrategy allocationStrategy)
The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance pools
specified by the EC2 Fleet launch configuration.
|
SpotOptionsRequest |
withAllocationStrategy(String allocationStrategy)
The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance pools
specified by the EC2 Fleet launch configuration.
|
SpotOptionsRequest |
withInstanceInterruptionBehavior(SpotInstanceInterruptionBehavior instanceInterruptionBehavior)
The behavior when a Spot Instance is interrupted.
|
SpotOptionsRequest |
withInstanceInterruptionBehavior(String instanceInterruptionBehavior)
The behavior when a Spot Instance is interrupted.
|
SpotOptionsRequest |
withInstancePoolsToUseCount(Integer instancePoolsToUseCount)
The number of Spot pools across which to allocate your target Spot capacity.
|
SpotOptionsRequest |
withMaintenanceStrategies(FleetSpotMaintenanceStrategiesRequest maintenanceStrategies)
The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
|
SpotOptionsRequest |
withMaxTotalPrice(String maxTotalPrice)
The maximum amount per hour for Spot Instances that you're willing to pay.
|
SpotOptionsRequest |
withMinTargetCapacity(Integer minTargetCapacity)
The minimum target capacity for Spot Instances in the fleet.
|
SpotOptionsRequest |
withSingleAvailabilityZone(Boolean singleAvailabilityZone)
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
|
SpotOptionsRequest |
withSingleInstanceType(Boolean singleInstanceType)
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
|
public void setAllocationStrategy(String allocationStrategy)
The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet launch configuration. For more information, see Allocation strategies for Spot Instances in the Amazon EC2 User Guide.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. EC2 Fleet then requests Spot Instances from the lowest priced of these pools.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are
launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance
of interruption in the near term. To give certain instance types a higher chance of launching first, use
capacity-optimized-prioritized. Set a priority for each instance type by using the
Priority parameter for LaunchTemplateOverrides. You can assign the same priority to
different LaunchTemplateOverrides. EC2 implements the priorities on a best-effort basis, but
optimizes for capacity first. capacity-optimized-prioritized is supported only if your EC2 Fleet
uses a launch template. Note that if the On-Demand AllocationStrategy is set to
prioritized, the same priority is applied when fulfilling On-Demand capacity.
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
We don't recommend the lowest-price allocation strategy because it has the highest risk of
interruption for your Spot Instances.
EC2 Fleet requests instances from the lowest priced Spot Instance pool that has available capacity. If the lowest priced pool doesn't have available capacity, the Spot Instances come from the next lowest priced pool that has available capacity. If a pool runs out of capacity before fulfilling your desired capacity, EC2 Fleet will continue to fulfill your request by drawing from the next lowest priced pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools. Because this strategy only considers instance price and not capacity availability, it might lead to high interruption rates.
Default: lowest-price
allocationStrategy - The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance
pools specified by the EC2 Fleet launch configuration. For more information, see Allocation
strategies for Spot Instances in the Amazon EC2 User Guide.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. EC2 Fleet then requests Spot Instances from the lowest priced of these pools.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are
launching. This means that we will request Spot Instances from the pools that we believe have the lowest
chance of interruption in the near term. To give certain instance types a higher chance of launching
first, use capacity-optimized-prioritized. Set a priority for each instance type by using the
Priority parameter for LaunchTemplateOverrides. You can assign the same priority
to different LaunchTemplateOverrides. EC2 implements the priorities on a best-effort basis,
but optimizes for capacity first. capacity-optimized-prioritized is supported only if your
EC2 Fleet uses a launch template. Note that if the On-Demand AllocationStrategy is set to
prioritized, the same priority is applied when fulfilling On-Demand capacity.
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
We don't recommend the lowest-price allocation strategy because it has the highest risk of
interruption for your Spot Instances.
EC2 Fleet requests instances from the lowest priced Spot Instance pool that has available capacity. If the lowest priced pool doesn't have available capacity, the Spot Instances come from the next lowest priced pool that has available capacity. If a pool runs out of capacity before fulfilling your desired capacity, EC2 Fleet will continue to fulfill your request by drawing from the next lowest priced pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools. Because this strategy only considers instance price and not capacity availability, it might lead to high interruption rates.
Default: lowest-price
SpotAllocationStrategypublic String getAllocationStrategy()
The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet launch configuration. For more information, see Allocation strategies for Spot Instances in the Amazon EC2 User Guide.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. EC2 Fleet then requests Spot Instances from the lowest priced of these pools.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are
launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance
of interruption in the near term. To give certain instance types a higher chance of launching first, use
capacity-optimized-prioritized. Set a priority for each instance type by using the
Priority parameter for LaunchTemplateOverrides. You can assign the same priority to
different LaunchTemplateOverrides. EC2 implements the priorities on a best-effort basis, but
optimizes for capacity first. capacity-optimized-prioritized is supported only if your EC2 Fleet
uses a launch template. Note that if the On-Demand AllocationStrategy is set to
prioritized, the same priority is applied when fulfilling On-Demand capacity.
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
We don't recommend the lowest-price allocation strategy because it has the highest risk of
interruption for your Spot Instances.
EC2 Fleet requests instances from the lowest priced Spot Instance pool that has available capacity. If the lowest priced pool doesn't have available capacity, the Spot Instances come from the next lowest priced pool that has available capacity. If a pool runs out of capacity before fulfilling your desired capacity, EC2 Fleet will continue to fulfill your request by drawing from the next lowest priced pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools. Because this strategy only considers instance price and not capacity availability, it might lead to high interruption rates.
Default: lowest-price
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. EC2 Fleet then requests Spot Instances from the lowest priced of these pools.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that
are launching. This means that we will request Spot Instances from the pools that we believe have the
lowest chance of interruption in the near term. To give certain instance types a higher chance of
launching first, use capacity-optimized-prioritized. Set a priority for each instance type
by using the Priority parameter for LaunchTemplateOverrides. You can assign the
same priority to different LaunchTemplateOverrides. EC2 implements the priorities on a
best-effort basis, but optimizes for capacity first. capacity-optimized-prioritized is
supported only if your EC2 Fleet uses a launch template. Note that if the On-Demand
AllocationStrategy is set to prioritized, the same priority is applied when
fulfilling On-Demand capacity.
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
We don't recommend the lowest-price allocation strategy because it has the highest risk of
interruption for your Spot Instances.
EC2 Fleet requests instances from the lowest priced Spot Instance pool that has available capacity. If the lowest priced pool doesn't have available capacity, the Spot Instances come from the next lowest priced pool that has available capacity. If a pool runs out of capacity before fulfilling your desired capacity, EC2 Fleet will continue to fulfill your request by drawing from the next lowest priced pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools. Because this strategy only considers instance price and not capacity availability, it might lead to high interruption rates.
Default: lowest-price
SpotAllocationStrategypublic SpotOptionsRequest withAllocationStrategy(String allocationStrategy)
The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet launch configuration. For more information, see Allocation strategies for Spot Instances in the Amazon EC2 User Guide.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. EC2 Fleet then requests Spot Instances from the lowest priced of these pools.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are
launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance
of interruption in the near term. To give certain instance types a higher chance of launching first, use
capacity-optimized-prioritized. Set a priority for each instance type by using the
Priority parameter for LaunchTemplateOverrides. You can assign the same priority to
different LaunchTemplateOverrides. EC2 implements the priorities on a best-effort basis, but
optimizes for capacity first. capacity-optimized-prioritized is supported only if your EC2 Fleet
uses a launch template. Note that if the On-Demand AllocationStrategy is set to
prioritized, the same priority is applied when fulfilling On-Demand capacity.
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
We don't recommend the lowest-price allocation strategy because it has the highest risk of
interruption for your Spot Instances.
EC2 Fleet requests instances from the lowest priced Spot Instance pool that has available capacity. If the lowest priced pool doesn't have available capacity, the Spot Instances come from the next lowest priced pool that has available capacity. If a pool runs out of capacity before fulfilling your desired capacity, EC2 Fleet will continue to fulfill your request by drawing from the next lowest priced pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools. Because this strategy only considers instance price and not capacity availability, it might lead to high interruption rates.
Default: lowest-price
allocationStrategy - The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance
pools specified by the EC2 Fleet launch configuration. For more information, see Allocation
strategies for Spot Instances in the Amazon EC2 User Guide.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. EC2 Fleet then requests Spot Instances from the lowest priced of these pools.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are
launching. This means that we will request Spot Instances from the pools that we believe have the lowest
chance of interruption in the near term. To give certain instance types a higher chance of launching
first, use capacity-optimized-prioritized. Set a priority for each instance type by using the
Priority parameter for LaunchTemplateOverrides. You can assign the same priority
to different LaunchTemplateOverrides. EC2 implements the priorities on a best-effort basis,
but optimizes for capacity first. capacity-optimized-prioritized is supported only if your
EC2 Fleet uses a launch template. Note that if the On-Demand AllocationStrategy is set to
prioritized, the same priority is applied when fulfilling On-Demand capacity.
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
We don't recommend the lowest-price allocation strategy because it has the highest risk of
interruption for your Spot Instances.
EC2 Fleet requests instances from the lowest priced Spot Instance pool that has available capacity. If the lowest priced pool doesn't have available capacity, the Spot Instances come from the next lowest priced pool that has available capacity. If a pool runs out of capacity before fulfilling your desired capacity, EC2 Fleet will continue to fulfill your request by drawing from the next lowest priced pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools. Because this strategy only considers instance price and not capacity availability, it might lead to high interruption rates.
Default: lowest-price
SpotAllocationStrategypublic SpotOptionsRequest withAllocationStrategy(SpotAllocationStrategy allocationStrategy)
The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet launch configuration. For more information, see Allocation strategies for Spot Instances in the Amazon EC2 User Guide.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. EC2 Fleet then requests Spot Instances from the lowest priced of these pools.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are
launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance
of interruption in the near term. To give certain instance types a higher chance of launching first, use
capacity-optimized-prioritized. Set a priority for each instance type by using the
Priority parameter for LaunchTemplateOverrides. You can assign the same priority to
different LaunchTemplateOverrides. EC2 implements the priorities on a best-effort basis, but
optimizes for capacity first. capacity-optimized-prioritized is supported only if your EC2 Fleet
uses a launch template. Note that if the On-Demand AllocationStrategy is set to
prioritized, the same priority is applied when fulfilling On-Demand capacity.
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
We don't recommend the lowest-price allocation strategy because it has the highest risk of
interruption for your Spot Instances.
EC2 Fleet requests instances from the lowest priced Spot Instance pool that has available capacity. If the lowest priced pool doesn't have available capacity, the Spot Instances come from the next lowest priced pool that has available capacity. If a pool runs out of capacity before fulfilling your desired capacity, EC2 Fleet will continue to fulfill your request by drawing from the next lowest priced pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools. Because this strategy only considers instance price and not capacity availability, it might lead to high interruption rates.
Default: lowest-price
allocationStrategy - The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance
pools specified by the EC2 Fleet launch configuration. For more information, see Allocation
strategies for Spot Instances in the Amazon EC2 User Guide.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. EC2 Fleet then requests Spot Instances from the lowest priced of these pools.
EC2 Fleet identifies the pools with the highest capacity availability for the number of instances that are
launching. This means that we will request Spot Instances from the pools that we believe have the lowest
chance of interruption in the near term. To give certain instance types a higher chance of launching
first, use capacity-optimized-prioritized. Set a priority for each instance type by using the
Priority parameter for LaunchTemplateOverrides. You can assign the same priority
to different LaunchTemplateOverrides. EC2 implements the priorities on a best-effort basis,
but optimizes for capacity first. capacity-optimized-prioritized is supported only if your
EC2 Fleet uses a launch template. Note that if the On-Demand AllocationStrategy is set to
prioritized, the same priority is applied when fulfilling On-Demand capacity.
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
We don't recommend the lowest-price allocation strategy because it has the highest risk of
interruption for your Spot Instances.
EC2 Fleet requests instances from the lowest priced Spot Instance pool that has available capacity. If the lowest priced pool doesn't have available capacity, the Spot Instances come from the next lowest priced pool that has available capacity. If a pool runs out of capacity before fulfilling your desired capacity, EC2 Fleet will continue to fulfill your request by drawing from the next lowest priced pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools. Because this strategy only considers instance price and not capacity availability, it might lead to high interruption rates.
Default: lowest-price
SpotAllocationStrategypublic void setMaintenanceStrategies(FleetSpotMaintenanceStrategiesRequest maintenanceStrategies)
The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
maintenanceStrategies - The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.public FleetSpotMaintenanceStrategiesRequest getMaintenanceStrategies()
The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
public SpotOptionsRequest withMaintenanceStrategies(FleetSpotMaintenanceStrategiesRequest maintenanceStrategies)
The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
maintenanceStrategies - The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.public void setInstanceInterruptionBehavior(String instanceInterruptionBehavior)
The behavior when a Spot Instance is interrupted.
Default: terminate
instanceInterruptionBehavior - The behavior when a Spot Instance is interrupted.
Default: terminate
SpotInstanceInterruptionBehaviorpublic String getInstanceInterruptionBehavior()
The behavior when a Spot Instance is interrupted.
Default: terminate
Default: terminate
SpotInstanceInterruptionBehaviorpublic SpotOptionsRequest withInstanceInterruptionBehavior(String instanceInterruptionBehavior)
The behavior when a Spot Instance is interrupted.
Default: terminate
instanceInterruptionBehavior - The behavior when a Spot Instance is interrupted.
Default: terminate
SpotInstanceInterruptionBehaviorpublic SpotOptionsRequest withInstanceInterruptionBehavior(SpotInstanceInterruptionBehavior instanceInterruptionBehavior)
The behavior when a Spot Instance is interrupted.
Default: terminate
instanceInterruptionBehavior - The behavior when a Spot Instance is interrupted.
Default: terminate
SpotInstanceInterruptionBehaviorpublic void setInstancePoolsToUseCount(Integer instancePoolsToUseCount)
The number of Spot pools across which to allocate your target Spot capacity. Supported only when Spot
AllocationStrategy is set to lowest-price. EC2 Fleet selects the cheapest Spot pools
and evenly allocates your target Spot capacity across the number of Spot pools that you specify.
Note that EC2 Fleet attempts to draw Spot Instances from the number of pools that you specify on a best effort basis. If a pool runs out of Spot capacity before fulfilling your target capacity, EC2 Fleet will continue to fulfill your request by drawing from the next cheapest pool. To ensure that your target capacity is met, you might receive Spot Instances from more than the number of pools that you specified. Similarly, if most of the pools have no Spot capacity, you might receive your full target capacity from fewer than the number of pools that you specified.
instancePoolsToUseCount - The number of Spot pools across which to allocate your target Spot capacity. Supported only when Spot
AllocationStrategy is set to lowest-price. EC2 Fleet selects the cheapest Spot
pools and evenly allocates your target Spot capacity across the number of Spot pools that you specify.
Note that EC2 Fleet attempts to draw Spot Instances from the number of pools that you specify on a best effort basis. If a pool runs out of Spot capacity before fulfilling your target capacity, EC2 Fleet will continue to fulfill your request by drawing from the next cheapest pool. To ensure that your target capacity is met, you might receive Spot Instances from more than the number of pools that you specified. Similarly, if most of the pools have no Spot capacity, you might receive your full target capacity from fewer than the number of pools that you specified.
public Integer getInstancePoolsToUseCount()
The number of Spot pools across which to allocate your target Spot capacity. Supported only when Spot
AllocationStrategy is set to lowest-price. EC2 Fleet selects the cheapest Spot pools
and evenly allocates your target Spot capacity across the number of Spot pools that you specify.
Note that EC2 Fleet attempts to draw Spot Instances from the number of pools that you specify on a best effort basis. If a pool runs out of Spot capacity before fulfilling your target capacity, EC2 Fleet will continue to fulfill your request by drawing from the next cheapest pool. To ensure that your target capacity is met, you might receive Spot Instances from more than the number of pools that you specified. Similarly, if most of the pools have no Spot capacity, you might receive your full target capacity from fewer than the number of pools that you specified.
AllocationStrategy is set to lowest-price. EC2 Fleet selects the cheapest Spot
pools and evenly allocates your target Spot capacity across the number of Spot pools that you
specify.
Note that EC2 Fleet attempts to draw Spot Instances from the number of pools that you specify on a best effort basis. If a pool runs out of Spot capacity before fulfilling your target capacity, EC2 Fleet will continue to fulfill your request by drawing from the next cheapest pool. To ensure that your target capacity is met, you might receive Spot Instances from more than the number of pools that you specified. Similarly, if most of the pools have no Spot capacity, you might receive your full target capacity from fewer than the number of pools that you specified.
public SpotOptionsRequest withInstancePoolsToUseCount(Integer instancePoolsToUseCount)
The number of Spot pools across which to allocate your target Spot capacity. Supported only when Spot
AllocationStrategy is set to lowest-price. EC2 Fleet selects the cheapest Spot pools
and evenly allocates your target Spot capacity across the number of Spot pools that you specify.
Note that EC2 Fleet attempts to draw Spot Instances from the number of pools that you specify on a best effort basis. If a pool runs out of Spot capacity before fulfilling your target capacity, EC2 Fleet will continue to fulfill your request by drawing from the next cheapest pool. To ensure that your target capacity is met, you might receive Spot Instances from more than the number of pools that you specified. Similarly, if most of the pools have no Spot capacity, you might receive your full target capacity from fewer than the number of pools that you specified.
instancePoolsToUseCount - The number of Spot pools across which to allocate your target Spot capacity. Supported only when Spot
AllocationStrategy is set to lowest-price. EC2 Fleet selects the cheapest Spot
pools and evenly allocates your target Spot capacity across the number of Spot pools that you specify.
Note that EC2 Fleet attempts to draw Spot Instances from the number of pools that you specify on a best effort basis. If a pool runs out of Spot capacity before fulfilling your target capacity, EC2 Fleet will continue to fulfill your request by drawing from the next cheapest pool. To ensure that your target capacity is met, you might receive Spot Instances from more than the number of pools that you specified. Similarly, if most of the pools have no Spot capacity, you might receive your full target capacity from fewer than the number of pools that you specified.
public void setSingleInstanceType(Boolean singleInstanceType)
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
Supported only for fleets of type instant.
singleInstanceType - Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
Supported only for fleets of type instant.
public Boolean getSingleInstanceType()
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
Supported only for fleets of type instant.
Supported only for fleets of type instant.
public SpotOptionsRequest withSingleInstanceType(Boolean singleInstanceType)
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
Supported only for fleets of type instant.
singleInstanceType - Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
Supported only for fleets of type instant.
public Boolean isSingleInstanceType()
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
Supported only for fleets of type instant.
Supported only for fleets of type instant.
public void setSingleAvailabilityZone(Boolean singleAvailabilityZone)
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
Supported only for fleets of type instant.
singleAvailabilityZone - Indicates that the fleet launches all Spot Instances into a single Availability Zone.
Supported only for fleets of type instant.
public Boolean getSingleAvailabilityZone()
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
Supported only for fleets of type instant.
Supported only for fleets of type instant.
public SpotOptionsRequest withSingleAvailabilityZone(Boolean singleAvailabilityZone)
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
Supported only for fleets of type instant.
singleAvailabilityZone - Indicates that the fleet launches all Spot Instances into a single Availability Zone.
Supported only for fleets of type instant.
public Boolean isSingleAvailabilityZone()
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
Supported only for fleets of type instant.
Supported only for fleets of type instant.
public void setMinTargetCapacity(Integer minTargetCapacity)
The minimum target capacity for Spot Instances in the fleet. If this minimum capacity isn't reached, no instances are launched.
Constraints: Maximum value of 1000. Supported only for fleets of type instant.
At least one of the following must be specified: SingleAvailabilityZone |
SingleInstanceType
minTargetCapacity - The minimum target capacity for Spot Instances in the fleet. If this minimum capacity isn't reached, no
instances are launched.
Constraints: Maximum value of 1000. Supported only for fleets of type instant.
At least one of the following must be specified: SingleAvailabilityZone |
SingleInstanceType
public Integer getMinTargetCapacity()
The minimum target capacity for Spot Instances in the fleet. If this minimum capacity isn't reached, no instances are launched.
Constraints: Maximum value of 1000. Supported only for fleets of type instant.
At least one of the following must be specified: SingleAvailabilityZone |
SingleInstanceType
Constraints: Maximum value of 1000. Supported only for fleets of type instant.
At least one of the following must be specified: SingleAvailabilityZone |
SingleInstanceType
public SpotOptionsRequest withMinTargetCapacity(Integer minTargetCapacity)
The minimum target capacity for Spot Instances in the fleet. If this minimum capacity isn't reached, no instances are launched.
Constraints: Maximum value of 1000. Supported only for fleets of type instant.
At least one of the following must be specified: SingleAvailabilityZone |
SingleInstanceType
minTargetCapacity - The minimum target capacity for Spot Instances in the fleet. If this minimum capacity isn't reached, no
instances are launched.
Constraints: Maximum value of 1000. Supported only for fleets of type instant.
At least one of the following must be specified: SingleAvailabilityZone |
SingleInstanceType
public void setMaxTotalPrice(String maxTotalPrice)
The maximum amount per hour for Spot Instances that you're willing to pay. We do not recommend using this parameter because it can lead to increased interruptions. If you do not specify this parameter, you will pay the current Spot price.
If you specify a maximum price, your Spot Instances will be interrupted more frequently than if you do not specify this parameter.
If your fleet includes T instances that are configured as unlimited, and if their average CPU usage
exceeds the baseline utilization, you will incur a charge for surplus credits. The MaxTotalPrice
does not account for surplus credits, and, if you use surplus credits, your final cost might be higher than what
you specified for MaxTotalPrice. For more information, see Surplus credits can incur charges in the Amazon EC2 User Guide.
maxTotalPrice - The maximum amount per hour for Spot Instances that you're willing to pay. We do not recommend using this
parameter because it can lead to increased interruptions. If you do not specify this parameter, you will
pay the current Spot price. If you specify a maximum price, your Spot Instances will be interrupted more frequently than if you do not specify this parameter.
If your fleet includes T instances that are configured as unlimited, and if their average CPU
usage exceeds the baseline utilization, you will incur a charge for surplus credits. The
MaxTotalPrice does not account for surplus credits, and, if you use surplus credits, your
final cost might be higher than what you specified for MaxTotalPrice. For more information,
see Surplus credits can incur charges in the Amazon EC2 User Guide.
public String getMaxTotalPrice()
The maximum amount per hour for Spot Instances that you're willing to pay. We do not recommend using this parameter because it can lead to increased interruptions. If you do not specify this parameter, you will pay the current Spot price.
If you specify a maximum price, your Spot Instances will be interrupted more frequently than if you do not specify this parameter.
If your fleet includes T instances that are configured as unlimited, and if their average CPU usage
exceeds the baseline utilization, you will incur a charge for surplus credits. The MaxTotalPrice
does not account for surplus credits, and, if you use surplus credits, your final cost might be higher than what
you specified for MaxTotalPrice. For more information, see Surplus credits can incur charges in the Amazon EC2 User Guide.
If you specify a maximum price, your Spot Instances will be interrupted more frequently than if you do not specify this parameter.
If your fleet includes T instances that are configured as unlimited, and if their average
CPU usage exceeds the baseline utilization, you will incur a charge for surplus credits. The
MaxTotalPrice does not account for surplus credits, and, if you use surplus credits, your
final cost might be higher than what you specified for MaxTotalPrice. For more information,
see Surplus credits can incur charges in the Amazon EC2 User Guide.
public SpotOptionsRequest withMaxTotalPrice(String maxTotalPrice)
The maximum amount per hour for Spot Instances that you're willing to pay. We do not recommend using this parameter because it can lead to increased interruptions. If you do not specify this parameter, you will pay the current Spot price.
If you specify a maximum price, your Spot Instances will be interrupted more frequently than if you do not specify this parameter.
If your fleet includes T instances that are configured as unlimited, and if their average CPU usage
exceeds the baseline utilization, you will incur a charge for surplus credits. The MaxTotalPrice
does not account for surplus credits, and, if you use surplus credits, your final cost might be higher than what
you specified for MaxTotalPrice. For more information, see Surplus credits can incur charges in the Amazon EC2 User Guide.
maxTotalPrice - The maximum amount per hour for Spot Instances that you're willing to pay. We do not recommend using this
parameter because it can lead to increased interruptions. If you do not specify this parameter, you will
pay the current Spot price. If you specify a maximum price, your Spot Instances will be interrupted more frequently than if you do not specify this parameter.
If your fleet includes T instances that are configured as unlimited, and if their average CPU
usage exceeds the baseline utilization, you will incur a charge for surplus credits. The
MaxTotalPrice does not account for surplus credits, and, if you use surplus credits, your
final cost might be higher than what you specified for MaxTotalPrice. For more information,
see Surplus credits can incur charges in the Amazon EC2 User Guide.
public String toString()
toString in class ObjectObject.toString()public SpotOptionsRequest clone()