Struct aws_sdk_ec2::model::FleetLaunchTemplateOverridesRequest

#[non_exhaustive]
pub struct FleetLaunchTemplateOverridesRequest {
    pub instance_type: Option<InstanceType>,
    pub max_price: Option<String>,
    pub subnet_id: Option<String>,
    pub availability_zone: Option<String>,
    pub weighted_capacity: Option<f64>,
    pub priority: Option<f64>,
    pub placement: Option<Placement>,
    pub instance_requirements: Option<InstanceRequirementsRequest>,
}

Describes overrides for a launch template.

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.

instance_type: Option<InstanceType>

The instance type.

If you specify InstanceTypes, you can't specify InstanceRequirements.

max_price: Option<String>

The maximum price per unit hour that you are willing to pay for a Spot Instance. 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 instances will be interrupted more frequently than if you do not specify this parameter.

subnet_id: Option<String>

The IDs of the subnets in which to launch the instances. Separate multiple subnet IDs using commas (for example, subnet-1234abcdeexample1, subnet-0987cdef6example2). A request of type instant can have only one subnet ID.

availability_zone: Option<String>

The Availability Zone in which to launch the instances.

weighted_capacity: Option<f64>

The number of units provided by the specified instance type.

priority: Option<f64>

The priority for the launch template override. The highest priority is launched first.

If the On-Demand AllocationStrategy is set to prioritized, EC2 Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity.

If the Spot AllocationStrategy is set to capacity-optimized-prioritized, EC2 Fleet uses priority on a best-effort basis to determine which launch template override to use in fulfilling Spot capacity, but optimizes for capacity first.

Valid values are whole numbers starting at 0. The lower the number, the higher the priority. If no number is set, the launch template override has the lowest priority. You can set the same priority for different launch template overrides.

placement: Option<Placement>

The location where the instance launched, if applicable.

instance_requirements: Option<InstanceRequirementsRequest>

The attributes for the instance types. When you specify instance attributes, Amazon EC2 will identify instance types with those attributes.

If you specify InstanceRequirements, you can't specify InstanceTypes.

Implementations

impl FleetLaunchTemplateOverridesRequest

pub fn instance_type(&self) -> Option<&InstanceType>

The instance type.

If you specify InstanceTypes, you can't specify InstanceRequirements.

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

The maximum price per unit hour that you are willing to pay for a Spot Instance. 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 instances will be interrupted more frequently than if you do not specify this parameter.

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

The IDs of the subnets in which to launch the instances. Separate multiple subnet IDs using commas (for example, subnet-1234abcdeexample1, subnet-0987cdef6example2). A request of type instant can have only one subnet ID.

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

The Availability Zone in which to launch the instances.

pub fn weighted_capacity(&self) -> Option<f64>

The number of units provided by the specified instance type.

pub fn priority(&self) -> Option<f64>

The priority for the launch template override. The highest priority is launched first.

If the On-Demand AllocationStrategy is set to prioritized, EC2 Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity.

If the Spot AllocationStrategy is set to capacity-optimized-prioritized, EC2 Fleet uses priority on a best-effort basis to determine which launch template override to use in fulfilling Spot capacity, but optimizes for capacity first.

Valid values are whole numbers starting at 0. The lower the number, the higher the priority. If no number is set, the launch template override has the lowest priority. You can set the same priority for different launch template overrides.

pub fn placement(&self) -> Option<&Placement>

The location where the instance launched, if applicable.

pub fn instance_requirements(&self) -> Option<&InstanceRequirementsRequest>

The attributes for the instance types. When you specify instance attributes, Amazon EC2 will identify instance types with those attributes.

If you specify InstanceRequirements, you can't specify InstanceTypes.

impl FleetLaunchTemplateOverridesRequest

pub fn builder() -> Builder

Creates a new builder-style object to manufacture FleetLaunchTemplateOverridesRequest.

Trait Implementations

impl Clone for FleetLaunchTemplateOverridesRequest

fn clone(&self) -> FleetLaunchTemplateOverridesRequest

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for FleetLaunchTemplateOverridesRequest

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

Formats the value using the given formatter.

impl PartialEq<FleetLaunchTemplateOverridesRequest> for FleetLaunchTemplateOverridesRequest

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

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

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

This method tests for !=.

impl StructuralPartialEq for FleetLaunchTemplateOverridesRequest