Copyright | (c) 2013-2023 Brendan Hay |
---|---|
License | Mozilla Public License, v. 2.0. |
Maintainer | Brendan Hay |
Stability | auto-generated |
Portability | non-portable (GHC extensions) |
Safe Haskell | Safe-Inferred |
Language | Haskell2010 |
Synopsis
- data SpotProvisioningSpecification = SpotProvisioningSpecification' {}
- newSpotProvisioningSpecification :: Natural -> SpotProvisioningTimeoutAction -> SpotProvisioningSpecification
- spotProvisioningSpecification_allocationStrategy :: Lens' SpotProvisioningSpecification (Maybe SpotProvisioningAllocationStrategy)
- spotProvisioningSpecification_blockDurationMinutes :: Lens' SpotProvisioningSpecification (Maybe Natural)
- spotProvisioningSpecification_timeoutDurationMinutes :: Lens' SpotProvisioningSpecification Natural
- spotProvisioningSpecification_timeoutAction :: Lens' SpotProvisioningSpecification SpotProvisioningTimeoutAction
Documentation
data SpotProvisioningSpecification Source #
The launch specification for Spot Instances in the instance fleet, which determines the defined duration, provisioning timeout behavior, and allocation strategy.
The instance fleet configuration is available only in Amazon EMR versions 4.8.0 and later, excluding 5.0.x versions. Spot Instance allocation strategy is available in Amazon EMR version 5.12.1 and later.
Spot Instances with a defined duration (also known as Spot blocks) are no longer available to new customers from July 1, 2021. For customers who have previously used the feature, we will continue to support Spot Instances with a defined duration until December 31, 2022.
See: newSpotProvisioningSpecification
smart constructor.
SpotProvisioningSpecification' | |
|
Instances
newSpotProvisioningSpecification Source #
Create a value of SpotProvisioningSpecification
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
$sel:allocationStrategy:SpotProvisioningSpecification'
, spotProvisioningSpecification_allocationStrategy
- Specifies the strategy to use in launching Spot Instance fleets.
Currently, the only option is capacity-optimized (the default), which
launches instances from Spot Instance pools with optimal capacity for
the number of instances that are launching.
$sel:blockDurationMinutes:SpotProvisioningSpecification'
, spotProvisioningSpecification_blockDurationMinutes
- The defined duration for Spot Instances (also known as Spot blocks) in
minutes. When specified, the Spot Instance does not terminate before the
defined duration expires, and defined duration pricing for Spot
Instances applies. Valid values are 60, 120, 180, 240, 300, or 360. The
duration period starts as soon as a Spot Instance receives its instance
ID. At the end of the duration, Amazon EC2 marks the Spot Instance for
termination and provides a Spot Instance termination notice, which gives
the instance a two-minute warning before it terminates.
Spot Instances with a defined duration (also known as Spot blocks) are no longer available to new customers from July 1, 2021. For customers who have previously used the feature, we will continue to support Spot Instances with a defined duration until December 31, 2022.
$sel:timeoutDurationMinutes:SpotProvisioningSpecification'
, spotProvisioningSpecification_timeoutDurationMinutes
- The spot provisioning timeout period in minutes. If Spot Instances are
not provisioned within this time period, the TimeOutAction
is taken.
Minimum value is 5 and maximum value is 1440. The timeout applies only
during initial provisioning, when the cluster is first created.
$sel:timeoutAction:SpotProvisioningSpecification'
, spotProvisioningSpecification_timeoutAction
- The action to take when TargetSpotCapacity
has not been fulfilled when
the TimeoutDurationMinutes
has expired; that is, when all Spot
Instances could not be provisioned within the Spot provisioning timeout.
Valid values are TERMINATE_CLUSTER
and SWITCH_TO_ON_DEMAND
.
SWITCH_TO_ON_DEMAND specifies that if no Spot Instances are available,
On-Demand Instances should be provisioned to fulfill any remaining Spot
capacity.
spotProvisioningSpecification_allocationStrategy :: Lens' SpotProvisioningSpecification (Maybe SpotProvisioningAllocationStrategy) Source #
Specifies the strategy to use in launching Spot Instance fleets. Currently, the only option is capacity-optimized (the default), which launches instances from Spot Instance pools with optimal capacity for the number of instances that are launching.
spotProvisioningSpecification_blockDurationMinutes :: Lens' SpotProvisioningSpecification (Maybe Natural) Source #
The defined duration for Spot Instances (also known as Spot blocks) in minutes. When specified, the Spot Instance does not terminate before the defined duration expires, and defined duration pricing for Spot Instances applies. Valid values are 60, 120, 180, 240, 300, or 360. The duration period starts as soon as a Spot Instance receives its instance ID. At the end of the duration, Amazon EC2 marks the Spot Instance for termination and provides a Spot Instance termination notice, which gives the instance a two-minute warning before it terminates.
Spot Instances with a defined duration (also known as Spot blocks) are no longer available to new customers from July 1, 2021. For customers who have previously used the feature, we will continue to support Spot Instances with a defined duration until December 31, 2022.
spotProvisioningSpecification_timeoutDurationMinutes :: Lens' SpotProvisioningSpecification Natural Source #
The spot provisioning timeout period in minutes. If Spot Instances are
not provisioned within this time period, the TimeOutAction
is taken.
Minimum value is 5 and maximum value is 1440. The timeout applies only
during initial provisioning, when the cluster is first created.
spotProvisioningSpecification_timeoutAction :: Lens' SpotProvisioningSpecification SpotProvisioningTimeoutAction Source #
The action to take when TargetSpotCapacity
has not been fulfilled when
the TimeoutDurationMinutes
has expired; that is, when all Spot
Instances could not be provisioned within the Spot provisioning timeout.
Valid values are TERMINATE_CLUSTER
and SWITCH_TO_ON_DEMAND
.
SWITCH_TO_ON_DEMAND specifies that if no Spot Instances are available,
On-Demand Instances should be provisioned to fulfill any remaining Spot
capacity.