You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using settings from 1c113ee, things fail botocore.exceptions.ClientError: An error occurred (InvalidParameterCombination) when calling the RequestSpotInstances operation: The request with type 'null' is not supported when instanceInterruptionBehavior is set to 'stop'.
Above happens because the action taken for a Spot Instance interruption depends on the request type (one-time or persistent) and the interruption behavior (hibernate, stop, or terminate).
A persistent Spot Instance request remains active until it expires or you cancel it, even if the request is fulfilled. If the Spot price exceeds your maximum price or capacity is not available, your Spot Instance is interrupted. After your instance is interrupted, when the maximum price exceeds the Spot price or capacity becomes available again, the Spot Instance is started (if stopped), the Spot Instance is resumed (if hibernated), or the Spot Instance request is opened again and Amazon EC2 launches a new Spot Instance (if terminated).
In summary, 'InstanceInterruptionBehavior' as 'Stop' will take effect only when the Spot Instance request is persistent.
Using settings from 1c113ee, things fail
botocore.exceptions.ClientError: An error occurred (InvalidParameterCombination) when calling the RequestSpotInstances operation: The request with type 'null' is not supported when instanceInterruptionBehavior is set to 'stop'.
However, AWS suggests it's possible with some extra settings
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html
cc @bearpelican
The text was updated successfully, but these errors were encountered: