Struct aws_sdk_ec2::types::SpotOptionsRequest
source · #[non_exhaustive]pub struct SpotOptionsRequest {
pub allocation_strategy: Option<SpotAllocationStrategy>,
pub maintenance_strategies: Option<FleetSpotMaintenanceStrategiesRequest>,
pub instance_interruption_behavior: Option<SpotInstanceInterruptionBehavior>,
pub instance_pools_to_use_count: Option<i32>,
pub single_instance_type: Option<bool>,
pub single_availability_zone: Option<bool>,
pub min_target_capacity: Option<i32>,
pub max_total_price: Option<String>,
}
Expand description
Describes the configuration of Spot Instances in an EC2 Fleet request.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.allocation_strategy: Option<SpotAllocationStrategy>
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.
- price-capacity-optimized (recommended)
-
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.
- capacity-optimized
-
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 thePriority
parameter forLaunchTemplateOverrides
. You can assign the same priority to differentLaunchTemplateOverrides
. 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-DemandAllocationStrategy
is set toprioritized
, the same priority is applied when fulfilling On-Demand capacity. - diversified
-
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
- lowest-price
-
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
maintenance_strategies: Option<FleetSpotMaintenanceStrategiesRequest>
The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
instance_interruption_behavior: Option<SpotInstanceInterruptionBehavior>
The behavior when a Spot Instance is interrupted.
Default: terminate
instance_pools_to_use_count: Option<i32>
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.
single_instance_type: Option<bool>
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
Supported only for fleets of type instant
.
single_availability_zone: Option<bool>
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
Supported only for fleets of type instant
.
min_target_capacity: Option<i32>
The minimum target capacity for Spot Instances in the fleet. If the minimum target capacity is not reached, the fleet launches no instances.
Supported only for fleets of type instant
.
At least one of the following must be specified: SingleAvailabilityZone
| SingleInstanceType
max_total_price: Option<String>
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.
Implementations§
source§impl SpotOptionsRequest
impl SpotOptionsRequest
sourcepub fn allocation_strategy(&self) -> Option<&SpotAllocationStrategy>
pub fn allocation_strategy(&self) -> Option<&SpotAllocationStrategy>
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.
- price-capacity-optimized (recommended)
-
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.
- capacity-optimized
-
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 thePriority
parameter forLaunchTemplateOverrides
. You can assign the same priority to differentLaunchTemplateOverrides
. 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-DemandAllocationStrategy
is set toprioritized
, the same priority is applied when fulfilling On-Demand capacity. - diversified
-
EC2 Fleet requests instances from all of the Spot Instance pools that you specify.
- lowest-price
-
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
sourcepub fn maintenance_strategies(
&self
) -> Option<&FleetSpotMaintenanceStrategiesRequest>
pub fn maintenance_strategies( &self ) -> Option<&FleetSpotMaintenanceStrategiesRequest>
The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
sourcepub fn instance_interruption_behavior(
&self
) -> Option<&SpotInstanceInterruptionBehavior>
pub fn instance_interruption_behavior( &self ) -> Option<&SpotInstanceInterruptionBehavior>
The behavior when a Spot Instance is interrupted.
Default: terminate
sourcepub fn instance_pools_to_use_count(&self) -> Option<i32>
pub fn instance_pools_to_use_count(&self) -> Option<i32>
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.
sourcepub fn single_instance_type(&self) -> Option<bool>
pub fn single_instance_type(&self) -> Option<bool>
Indicates that the fleet uses a single instance type to launch all Spot Instances in the fleet.
Supported only for fleets of type instant
.
sourcepub fn single_availability_zone(&self) -> Option<bool>
pub fn single_availability_zone(&self) -> Option<bool>
Indicates that the fleet launches all Spot Instances into a single Availability Zone.
Supported only for fleets of type instant
.
sourcepub fn min_target_capacity(&self) -> Option<i32>
pub fn min_target_capacity(&self) -> Option<i32>
The minimum target capacity for Spot Instances in the fleet. If the minimum target capacity is not reached, the fleet launches no instances.
Supported only for fleets of type instant
.
At least one of the following must be specified: SingleAvailabilityZone
| SingleInstanceType
sourcepub fn max_total_price(&self) -> Option<&str>
pub fn max_total_price(&self) -> Option<&str>
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.
source§impl SpotOptionsRequest
impl SpotOptionsRequest
sourcepub fn builder() -> SpotOptionsRequestBuilder
pub fn builder() -> SpotOptionsRequestBuilder
Creates a new builder-style object to manufacture SpotOptionsRequest
.
Trait Implementations§
source§impl Clone for SpotOptionsRequest
impl Clone for SpotOptionsRequest
source§fn clone(&self) -> SpotOptionsRequest
fn clone(&self) -> SpotOptionsRequest
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Debug for SpotOptionsRequest
impl Debug for SpotOptionsRequest
source§impl PartialEq<SpotOptionsRequest> for SpotOptionsRequest
impl PartialEq<SpotOptionsRequest> for SpotOptionsRequest
source§fn eq(&self, other: &SpotOptionsRequest) -> bool
fn eq(&self, other: &SpotOptionsRequest) -> bool
self
and other
values to be equal, and is used
by ==
.