Struct aws_sdk_ec2::types::LaunchTemplateOverrides
source · #[non_exhaustive]pub struct LaunchTemplateOverrides {
pub instance_type: Option<InstanceType>,
pub spot_price: Option<String>,
pub subnet_id: Option<String>,
pub availability_zone: Option<String>,
pub weighted_capacity: Option<f64>,
pub priority: Option<f64>,
pub instance_requirements: Option<InstanceRequirements>,
}
Expand description
Describes overrides for a launch template.
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.instance_type: Option<InstanceType>
The instance type.
spot_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 ID of the subnet in which to launch the instances.
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 OnDemandAllocationStrategy
is set to prioritized
, Spot Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity.
If the Spot AllocationStrategy
is set to capacityOptimizedPrioritized
, Spot 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.
instance_requirements: Option<InstanceRequirements>
The instance requirements. When you specify instance requirements, Amazon EC2 will identify instance types with the provided requirements, and then use your On-Demand and Spot allocation strategies to launch instances from these instance types, in the same way as when you specify a list of instance types.
If you specify InstanceRequirements
, you can't specify InstanceType
.
Implementations§
source§impl LaunchTemplateOverrides
impl LaunchTemplateOverrides
sourcepub fn instance_type(&self) -> Option<&InstanceType>
pub fn instance_type(&self) -> Option<&InstanceType>
The instance type.
sourcepub fn spot_price(&self) -> Option<&str>
pub fn spot_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.
sourcepub fn availability_zone(&self) -> Option<&str>
pub fn availability_zone(&self) -> Option<&str>
The Availability Zone in which to launch the instances.
sourcepub fn weighted_capacity(&self) -> Option<f64>
pub fn weighted_capacity(&self) -> Option<f64>
The number of units provided by the specified instance type.
sourcepub fn priority(&self) -> Option<f64>
pub fn priority(&self) -> Option<f64>
The priority for the launch template override. The highest priority is launched first.
If OnDemandAllocationStrategy
is set to prioritized
, Spot Fleet uses priority to determine which launch template override to use first in fulfilling On-Demand capacity.
If the Spot AllocationStrategy
is set to capacityOptimizedPrioritized
, Spot 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.
sourcepub fn instance_requirements(&self) -> Option<&InstanceRequirements>
pub fn instance_requirements(&self) -> Option<&InstanceRequirements>
The instance requirements. When you specify instance requirements, Amazon EC2 will identify instance types with the provided requirements, and then use your On-Demand and Spot allocation strategies to launch instances from these instance types, in the same way as when you specify a list of instance types.
If you specify InstanceRequirements
, you can't specify InstanceType
.
source§impl LaunchTemplateOverrides
impl LaunchTemplateOverrides
sourcepub fn builder() -> LaunchTemplateOverridesBuilder
pub fn builder() -> LaunchTemplateOverridesBuilder
Creates a new builder-style object to manufacture LaunchTemplateOverrides
.
Trait Implementations§
source§impl Clone for LaunchTemplateOverrides
impl Clone for LaunchTemplateOverrides
source§fn clone(&self) -> LaunchTemplateOverrides
fn clone(&self) -> LaunchTemplateOverrides
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Debug for LaunchTemplateOverrides
impl Debug for LaunchTemplateOverrides
source§impl PartialEq<LaunchTemplateOverrides> for LaunchTemplateOverrides
impl PartialEq<LaunchTemplateOverrides> for LaunchTemplateOverrides
source§fn eq(&self, other: &LaunchTemplateOverrides) -> bool
fn eq(&self, other: &LaunchTemplateOverrides) -> bool
self
and other
values to be equal, and is used
by ==
.