pub struct SpotFleetRequestResult {Show 28 fields
pub allocation_strategy: Output<Option<String>>,
pub client_token: Output<String>,
pub context: Output<Option<String>>,
pub excess_capacity_termination_policy: Output<Option<String>>,
pub fleet_type: Output<Option<String>>,
pub iam_fleet_role: Output<String>,
pub instance_interruption_behaviour: Output<Option<String>>,
pub instance_pools_to_use_count: Output<Option<i32>>,
pub launch_specifications: Output<Option<Vec<SpotFleetRequestLaunchSpecification>>>,
pub launch_template_configs: Output<Option<Vec<SpotFleetRequestLaunchTemplateConfig>>>,
pub load_balancers: Output<Vec<String>>,
pub on_demand_allocation_strategy: Output<Option<String>>,
pub on_demand_max_total_price: Output<Option<String>>,
pub on_demand_target_capacity: Output<Option<i32>>,
pub replace_unhealthy_instances: Output<Option<bool>>,
pub spot_maintenance_strategies: Output<Option<SpotFleetRequestSpotMaintenanceStrategies>>,
pub spot_price: Output<Option<String>>,
pub spot_request_state: Output<String>,
pub tags: Output<Option<HashMap<String, String>>>,
pub tags_all: Output<HashMap<String, String>>,
pub target_capacity: Output<i32>,
pub target_capacity_unit_type: Output<Option<String>>,
pub target_group_arns: Output<Vec<String>>,
pub terminate_instances_on_delete: Output<Option<String>>,
pub terminate_instances_with_expiration: Output<Option<bool>>,
pub valid_from: Output<Option<String>>,
pub valid_until: Output<Option<String>>,
pub wait_for_fulfillment: Output<Option<bool>>,
}Fields§
§allocation_strategy: Output<Option<String>>Indicates how to allocate the target capacity across
the Spot pools specified by the Spot fleet request. Valid values: lowestPrice, diversified, capacityOptimized, capacityOptimizedPrioritized, and priceCapacityOptimized. The default is
lowestPrice.
client_token: Output<String>§context: Output<Option<String>>Reserved.
excess_capacity_termination_policy: Output<Option<String>>Indicates whether running Spot instances should be terminated if the target capacity of the Spot fleet request is decreased below the current size of the Spot fleet.
fleet_type: Output<Option<String>>The type of fleet request. Indicates whether the Spot Fleet only requests the target
capacity or also attempts to maintain it. Default is maintain.
iam_fleet_role: Output<String>Grants the Spot fleet permission to terminate Spot instances on your behalf when you cancel its Spot fleet request using CancelSpotFleetRequests or when the Spot fleet request expires, if you set terminateInstancesWithExpiration.
instance_interruption_behaviour: Output<Option<String>>Indicates whether a Spot
instance stops or terminates when it is interrupted. Default is
terminate.
instance_pools_to_use_count: Output<Option<i32>>The number of Spot pools across which to allocate your target Spot capacity.
Valid only when allocation_strategy is set to lowestPrice. Spot Fleet selects
the cheapest Spot pools and evenly allocates your target Spot capacity across
the number of Spot pools that you specify.
launch_specifications: Output<Option<Vec<SpotFleetRequestLaunchSpecification>>>Used to define the launch configuration of the
spot-fleet request. Can be specified multiple times to define different bids
across different markets and instance types. Conflicts with launch_template_config. At least one of launch_specification or launch_template_config is required.
Note: This takes in similar but not
identical inputs as aws.ec2.Instance. There are limitations on
what you can specify. See the list of officially supported inputs in the
reference documentation. Any normal aws.ec2.Instance parameter that corresponds to those inputs may be used and it have
a additional parameter iam_instance_profile_arn takes aws.iam.InstanceProfile attribute arn as input.
launch_template_configs: Output<Option<Vec<SpotFleetRequestLaunchTemplateConfig>>>Launch template configuration block. See Launch Template Configs below for more details. Conflicts with launch_specification. At least one of launch_specification or launch_template_config is required.
load_balancers: Output<Vec<String>>A list of elastic load balancer names to add to the Spot fleet.
on_demand_allocation_strategy: Output<Option<String>>The order of the launch template overrides to use in fulfilling On-Demand capacity. the possible values are: lowestPrice and prioritized. the default is lowestPrice.
on_demand_max_total_price: Output<Option<String>>The maximum amount per hour for On-Demand Instances that you’re willing to pay. When the maximum amount you’re willing to pay is reached, the fleet stops launching instances even if it hasn’t met the target capacity.
on_demand_target_capacity: Output<Option<i32>>The number of On-Demand units to request. If the request type is maintain, you can specify a target capacity of 0 and add capacity later.
replace_unhealthy_instances: Output<Option<bool>>Indicates whether Spot fleet should replace unhealthy instances. Default false.
spot_maintenance_strategies: Output<Option<SpotFleetRequestSpotMaintenanceStrategies>>Nested argument containing maintenance strategies for managing your Spot Instances that are at an elevated risk of being interrupted. Defined below.
spot_price: Output<Option<String>>The maximum bid price per unit hour.
spot_request_state: Output<String>The state of the Spot fleet request.
A map of tags to assign to the resource. .If configured with a provider default_tags configuration block present, tags with matching keys will overwrite those defined at the provider-level.
A map of tags assigned to the resource, including those inherited from the provider default_tags configuration block.
target_capacity: Output<i32>The number of units to request. You can choose to set the target capacity in terms of instances or a performance characteristic that is important to your application workload, such as vCPUs, memory, or I/O.
target_capacity_unit_type: Output<Option<String>>The unit for the target capacity. This can only be done with instance_requirements defined
target_group_arns: Output<Vec<String>>A list of aws.alb.TargetGroup ARNs, for use with Application Load Balancing.
terminate_instances_on_delete: Output<Option<String>>Indicates whether running Spot
instances should be terminated when the resource is deleted (and the Spot fleet request cancelled).
If no value is specified, the value of the terminate_instances_with_expiration argument is used.
terminate_instances_with_expiration: Output<Option<bool>>Indicates whether running Spot instances should be terminated when the Spot fleet request expires.
valid_from: Output<Option<String>>The start date and time of the request, in UTC RFC3339 format(for example, YYYY-MM-DDTHH:MM:SSZ). The default is to start fulfilling the request immediately.
valid_until: Output<Option<String>>The end date and time of the request, in UTC RFC3339 format(for example, YYYY-MM-DDTHH:MM:SSZ). At this point, no new Spot instance requests are placed or enabled to fulfill the request.
wait_for_fulfillment: Output<Option<bool>>If set, this provider will wait for the Spot Request to be fulfilled, and will throw an error if the timeout of 10m is reached.