The replacement strategy to use. Only available for fleets of type maintain
.launch
- Spot Fleet launches a new replacement Spot Instance when a rebalance notification is emitted for an existing Spot Instance in the fleet. Spot Fleet does not terminate the instances that receive a rebalance notification. You can terminate the old instances, or you can leave them running. You are charged for all instances while they are running. launch-before-terminate
- Spot Fleet launches a new replacement Spot Instance when a rebalance notification is emitted for an existing Spot Instance in the fleet, and then, after a delay that you specify (in TerminationDelay
), terminates the instances that received a rebalance notification.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Aliases | SpotFleetRequestConfig_SpotMaintenanceStrategies_CapacityRebalance_ReplacementStrategy |
-CapacityRebalance_TerminationDelay <
Int32>
The amount of time (in seconds) that Amazon EC2 waits before terminating the old Spot Instance after launching a new replacement Spot Instance.Required when ReplacementStrategy
is set to launch-before-terminate
.Not valid when ReplacementStrategy
is set to launch
.Valid values: Minimum value of 120
seconds. Maximum value of 7200
seconds.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Aliases | SpotFleetRequestConfig_SpotMaintenanceStrategies_CapacityRebalance_TerminationDelay |
One or more Classic Load Balancers.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Aliases | SpotFleetRequestConfig_LoadBalancersConfig_ClassicLoadBalancersConfig_ClassicLoadBalancers |
Amazon.PowerShell.Cmdlets.EC2.AmazonEC2ClientCmdlet.ClientConfig
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
This parameter overrides confirmation prompts to force the cmdlet to continue its operation. This parameter should always be used with caution.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Changes the cmdlet behavior to return the value passed to the SpotFleetRequestConfig_SpotPrice parameter. The -PassThru parameter is deprecated, use -Select '^SpotFleetRequestConfig_SpotPrice' instead. This parameter will be removed in a future version.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Use the -Select parameter to control the cmdlet output. The default value is '*'. Specifying -Select '*' will result in the cmdlet returning the whole service response (Amazon.EC2.Model.RequestSpotFleetResponse). Specifying the name of a property of type Amazon.EC2.Model.RequestSpotFleetResponse will result in that property being returned. Specifying -Select '^ParameterName' will result in the cmdlet returning the selected cmdlet parameter value.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
The strategy that determines how to allocate the target Spot Instance capacity across the Spot Instance pools specified by the Spot Fleet launch configuration. For more information, see
Allocation strategies for Spot Instances in the
Amazon EC2 User Guide.
- priceCapacityOptimized (recommended)
- Spot Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. Spot Fleet then requests Spot Instances from the lowest priced of these pools.
- capacityOptimized
- Spot Fleet identifies the pools with the highest capacity availability for the number of instances that are launching. This means that we will request Spot Instances from the pools that we believe have the lowest chance of interruption in the near term. To give certain instance types a higher chance of launching first, use
capacityOptimizedPrioritized
. 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. capacityOptimizedPrioritized
is supported only if your Spot Fleet uses a launch template. Note that if the OnDemandAllocationStrategy
is set to prioritized
, the same priority is applied when fulfilling On-Demand capacity. - diversified
- Spot Fleet requests instances from all of the Spot Instance pools that you specify.
- lowestPrice
- Spot Fleet requests instances from the lowest priced Spot Instance pool that has available capacity. If the lowest priced pool doesn't have available capacity, the Spot Instances come from the next lowest priced pool that has available capacity. If a pool runs out of capacity before fulfilling your desired capacity, Spot Fleet will continue to fulfill your request by drawing from the next lowest priced pool. To ensure that your desired capacity is met, you might receive Spot Instances from several pools. Because this strategy only considers instance price and not capacity availability, it might lead to high interruption rates.
Default:
lowestPrice
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_ClientToken <
String>
A unique, case-sensitive identifier that you provide to ensure the idempotency of your listings. This helps to avoid duplicate listings. For more information, see
Ensuring Idempotency.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_Context <
String>
Reserved.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Indicates whether running instances should be terminated if you decrease the target capacity of the Spot Fleet request below the current size of the Spot Fleet.Supported only for fleets of type maintain
.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_FulfilledCapacity <
Double>
The number of units fulfilled by this request compared to the set target capacity. You cannot set this value.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_IamFleetRole <
String>
The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) role that grants the Spot Fleet the permission to request, launch, terminate, and tag instances on your behalf. For more information, see
Spot Fleet prerequisites in the
Amazon EC2 User Guide. Spot Fleet can 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
.
Required? | True |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
The behavior when a Spot Instance is interrupted. The default is terminate
.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_InstancePoolsToUseCount <
Int32>
The number of Spot pools across which to allocate your target Spot capacity. Valid only when Spot AllocationStrategy is set to lowest-price
. Spot Fleet selects the cheapest Spot pools and evenly allocates your target Spot capacity across the number of Spot pools that you specify.Note that Spot 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, Spot 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.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
The launch specifications for the Spot Fleet request. If you specify LaunchSpecifications
, you can't specify LaunchTemplateConfigs
. If you include On-Demand capacity in your request, you must use LaunchTemplateConfigs
.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Aliases | SpotFleetRequestConfig_LaunchSpecifications |
The launch template and overrides. If you specify LaunchTemplateConfigs
, you can't specify LaunchSpecifications
. If you include On-Demand capacity in your request, you must use LaunchTemplateConfigs
.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Aliases | SpotFleetRequestConfig_LaunchTemplateConfigs |
The order of the launch template overrides to use in fulfilling On-Demand capacity. If you specify lowestPrice
, Spot Fleet uses price to determine the order, launching the lowest price first. If you specify prioritized
, Spot Fleet uses the priority that you assign to each Spot Fleet launch template override, launching the highest priority first. If you do not specify a value, Spot Fleet defaults to lowestPrice
.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_OnDemandFulfilledCapacity <
Double>
The number of On-Demand units fulfilled by this request compared to the set target On-Demand capacity.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_OnDemandMaxTotalPrice <
String>
The maximum amount per hour for On-Demand Instances that you're willing to pay. You can use the onDemandMaxTotalPrice
parameter, the spotMaxTotalPrice
parameter, or both parameters to ensure that your fleet cost does not exceed your budget. If you set a maximum price per hour for the On-Demand Instances and Spot Instances in your request, Spot Fleet will launch instances until it reaches the maximum amount 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.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_OnDemandTargetCapacity <
Int32>
The number of On-Demand 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. If the request type is maintain
, you can specify a target capacity of 0 and add capacity later.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_ReplaceUnhealthyInstance <
Boolean>
Indicates whether Spot Fleet should replace unhealthy instances.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Aliases | SpotFleetRequestConfig_ReplaceUnhealthyInstances |
-SpotFleetRequestConfig_SpotMaxTotalPrice <
String>
The maximum amount per hour for Spot Instances that you're willing to pay. You can use the spotdMaxTotalPrice
parameter, the onDemandMaxTotalPrice
parameter, or both parameters to ensure that your fleet cost does not exceed your budget. If you set a maximum price per hour for the On-Demand Instances and Spot Instances in your request, Spot Fleet will launch instances until it reaches the maximum amount 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.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_SpotPrice <
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. Required? | False |
Position? | 1 |
Accept pipeline input? | True (ByValue, ByPropertyName) |
The key-value pair for tagging the Spot Fleet request on creation. The value for
ResourceType
must be
spot-fleet-request
, otherwise the Spot Fleet request fails. To tag instances at launch, specify the tags in the
launch template (valid only if you use
LaunchTemplateConfigs
) or in the
SpotFleetTagSpecification
(valid only if you use
LaunchSpecifications
). For information about tagging after launch, see
Tagging Your Resources.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Aliases | SpotFleetRequestConfig_TagSpecifications |
-SpotFleetRequestConfig_TargetCapacity <
Int32>
The number of units to request for the Spot Fleet. 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. If the request type is maintain
, you can specify a target capacity of 0 and add capacity later.
Required? | True |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
The unit for the target capacity. TargetCapacityUnitType
can only be specified when InstanceRequirements
is specified.Default: units
(translates to number of instances)
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_TerminateInstancesWithExpiration <
Boolean>
Indicates whether running Spot Instances are terminated when the Spot Fleet request expires.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
The type of request. Indicates whether the Spot Fleet only requests the target capacity or also attempts to maintain it. When this value is request
, the Spot Fleet only places the required requests. It does not attempt to replenish Spot Instances if capacity is diminished, nor does it submit requests in alternative Spot pools if capacity is not available. When this value is maintain
, the Spot Fleet maintains the target capacity. The Spot Fleet places the required requests to meet capacity and automatically replenishes any interrupted instances. Default: maintain
. instant
is listed but is not used by Spot Fleet.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_UtcValidFrom <DateTime>
The start date and time of the request, in UTC format (YYYY-MM-DDTHH:MM:SSZ). By default, Amazon EC2 starts fulfilling the request immediately.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_UtcValidUntil <DateTime>
The end date and time of the request, in UTC format (YYYY-MM-DDTHH:MM:SSZ). After the end date and time, no new Spot Instance requests are placed or able to fulfill the request. If no value is specified, the Spot Fleet request remains until you cancel it.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_ValidFrom <DateTime>
This property is deprecated. Setting this property results in non-UTC DateTimes not being marshalled correctly. Use ValidFromUtc instead. Setting either ValidFrom or ValidFromUtc results in both ValidFrom and ValidFromUtc being assigned, the latest assignment to either one of the two property is reflected in the value of both. ValidFrom is provided for backwards compatibility only and assigning a non-Utc DateTime to it results in the wrong timestamp being passed to the service.The start date and time of the request, in UTC format (YYYY-MM-DDTHH:MM:SSZ). By default, Amazon EC2 starts fulfilling the request immediately.This parameter is deprecated.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
-SpotFleetRequestConfig_ValidUntil <DateTime>
This property is deprecated. Setting this property results in non-UTC DateTimes not being marshalled correctly. Use ValidUntilUtc instead. Setting either ValidUntil or ValidUntilUtc results in both ValidUntil and ValidUntilUtc being assigned, the latest assignment to either one of the two property is reflected in the value of both. ValidUntil is provided for backwards compatibility only and assigning a non-Utc DateTime to it results in the wrong timestamp being passed to the service.The end date and time of the request, in UTC format (YYYY-MM-DDTHH:MM:SSZ). After the end date and time, no new Spot Instance requests are placed or able to fulfill the request. If no value is specified, the Spot Fleet request remains until you cancel it.This parameter is deprecated.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
One or more target groups.
Required? | False |
Position? | Named |
Accept pipeline input? | True (ByPropertyName) |
Aliases | SpotFleetRequestConfig_LoadBalancersConfig_TargetGroupsConfig_TargetGroups |