Struct aws_sdk_ec2::model::SpotOptionsRequest

#[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>,
}

Describes the configuration of Spot Instances in an EC2 Fleet request.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

allocation_strategy: Option<SpotAllocationStrategy>

Indicates how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet.

If the allocation strategy is lowest-price, EC2 Fleet launches instances from the Spot Instance pools with the lowest price. This is the default allocation strategy.

If the allocation strategy is diversified, EC2 Fleet launches instances from all of the Spot Instance pools that you specify.

If the allocation strategy is capacity-optimized (recommended), EC2 Fleet launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching. 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 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.

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. The default is terminate.

instance_pools_to_use_count: Option<i32>

The number of Spot pools across which to allocate your target Spot capacity. Valid 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.

max_total_price: Option<String>

The maximum amount per hour for Spot Instances that you're willing to pay.

Implementations

impl SpotOptionsRequest

pub fn allocation_strategy(&self) -> Option<&SpotAllocationStrategy>

Indicates how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the EC2 Fleet.

If the allocation strategy is lowest-price, EC2 Fleet launches instances from the Spot Instance pools with the lowest price. This is the default allocation strategy.

If the allocation strategy is diversified, EC2 Fleet launches instances from all of the Spot Instance pools that you specify.

If the allocation strategy is capacity-optimized (recommended), EC2 Fleet launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching. 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 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.

pub fn maintenance_strategies(
    &self
) -> Option<&FleetSpotMaintenanceStrategiesRequest>

The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.

pub fn instance_interruption_behavior(
    &self
) -> Option<&SpotInstanceInterruptionBehavior>

The behavior when a Spot Instance is interrupted. The default is terminate.

pub fn instance_pools_to_use_count(&self) -> Option<i32>

The number of Spot pools across which to allocate your target Spot capacity. Valid 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.

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.

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.

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.

pub fn max_total_price(&self) -> Option<&str>

The maximum amount per hour for Spot Instances that you're willing to pay.

impl SpotOptionsRequest

pub fn builder() -> Builder

Creates a new builder-style object to manufacture SpotOptionsRequest

Trait Implementations

impl Clone for SpotOptionsRequest

fn clone(&self) -> SpotOptionsRequest

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for SpotOptionsRequest

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq<SpotOptionsRequest> for SpotOptionsRequest

fn eq(&self, other: &SpotOptionsRequest) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &SpotOptionsRequest) -> bool

This method tests for !=.

impl StructuralPartialEq for SpotOptionsRequest