Struct aws_sdk_ec2::model::SpotOptionsRequest

source · [−]

#[non_exhaustive]
pub struct SpotOptionsRequest { /* private fields */ }

Expand description

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

Implementations

source

impl SpotOptionsRequest

source

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.

lowest-price - EC2 Fleet launches instances from the lowest-price Spot Instance pool that has available capacity. If the cheapest pool doesn't have available capacity, the Spot Instances come from the next cheapest 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 cheapest pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools.

diversified - EC2 Fleet launches instances from all of the Spot Instance pools that you specify.

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.

Default: lowest-price

source

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

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

source

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

The behavior when a Spot Instance is interrupted.

Default: terminate

source

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.

source

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.

source

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.

source

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

source

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