Mixing
![Cardinality of $[lambda]^kappa$](https://lh5.googleusercontent.com/-ducgR7jqsoc/AAAAAAAAAAI/AAAAAAAAAAA/AKxrwcbUk6OL8Ko1jZi19yTOET-VidQQOQ/s72-c-mo/photo.jpg?sz=32)
Change interruption behavior of fulfilled AWS spot request
Before knowing exactly how AWS spot instances work I configured a spot request with the interruption behavior set to terminate. As I understand it my running instance state will be deleted on termination. So if I don't have an image backup I will not be able to start the server again in it's last state.
Since the spot request is fulfilled and the instance running, is it possible to change the interruption behavior to stop when I am outbid? I cant seem to find the option to change the interruption behavior.
amazon-web-services amazon-ec2
asked Nov 22 '18 at 7:25
RynardtRynardt
4,17072241
add a comment |
Before knowing exactly how AWS spot instances work I configured a spot request with the interruption behavior set to terminate. As I understand it my running instance state will be deleted on termination. So if I don't have an image backup I will not be able to start the server again in it's last state.
Since the spot request is fulfilled and the instance running, is it possible to change the interruption behavior to stop when I am outbid? I cant seem to find the option to change the interruption behavior.
amazon-web-services amazon-ec2
asked Nov 22 '18 at 7:25
RynardtRynardt
4,17072241
add a comment |
Before knowing exactly how AWS spot instances work I configured a spot request with the interruption behavior set to terminate. As I understand it my running instance state will be deleted on termination. So if I don't have an image backup I will not be able to start the server again in it's last state.
Since the spot request is fulfilled and the instance running, is it possible to change the interruption behavior to stop when I am outbid? I cant seem to find the option to change the interruption behavior.
amazon-web-services amazon-ec2
asked Nov 22 '18 at 7:25
RynardtRynardt
4,17072241
Before knowing exactly how AWS spot instances work I configured a spot request with the interruption behavior set to terminate. As I understand it my running instance state will be deleted on termination. So if I don't have an image backup I will not be able to start the server again in it's last state.
Since the spot request is fulfilled and the instance running, is it possible to change the interruption behavior to stop when I am outbid? I cant seem to find the option to change the interruption behavior.
amazon-web-services amazon-ec2
amazon-web-services amazon-ec2
asked Nov 22 '18 at 7:25
RynardtRynardt
4,17072241
asked Nov 22 '18 at 7:25
RynardtRynardt
4,17072241
asked Nov 22 '18 at 7:25
RynardtRynardt
4,17072241
asked Nov 22 '18 at 7:25
RynardtRynardt
4,17072241
asked Nov 22 '18 at 7:25
RynardtRynardt
4,17072241
4,17072241
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
According to boto3 Spot instance creation documentation, you may also instruct the instance to stop or hibernate if you set the instance type to persistent. The default behaviour is terminate. This features is added in November 2017.
response = client.request_spot_fleet(
SpotFleetRequestConfig={
.....
Type='one-time'|'persistent',
'InstanceInterruptionBehavior': 'hibernate'|'stop'|'terminate'
}
Use them sparingly as each behaviour has some pros and cons, e.g. you must take care of process network connection interruption if yo use hibernate. For stop, you may want to store data into another mounted EBS.
answered Nov 22 '18 at 8:23
mootmootmootmoot
6,38622037
Can I change the instance type from one time to persistent without terminating the spot instance?
– Rynardt
Nov 22 '18 at 9:27
1
@Rynardt Well, you didn't see the option inside AWS Console, it means it is not changeable at the moment.
– mootmoot
Nov 22 '18 at 9:44
add a comment |
For setting the interruption behavior to stop, we need to take care of some requirements:
- For a Spot Instance request, the type must be persistent, not
one-time. You cannot specify a launch group in the Spot Instance
request. - For a Spot Fleet request, the type must be maintain, not request.
- The root volume must be an EBS volume, not an instance store volume.
by following the above requirements, we can change the interruption behavior from terminate to stop.
Please refer the following url for reference:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html
answered Nov 22 '18 at 8:54
Dharmesh PurohitDharmesh Purohit
963
My Spot Instance request is currently one-time and not persistent. How do I change it without terminating the running instance?
– Rynardt
Nov 22 '18 at 9:26
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53425796%2fchange-interruption-behavior-of-fulfilled-aws-spot-request%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
According to boto3 Spot instance creation documentation, you may also instruct the instance to stop or hibernate if you set the instance type to persistent. The default behaviour is terminate. This features is added in November 2017.
response = client.request_spot_fleet(
SpotFleetRequestConfig={
.....
Type='one-time'|'persistent',
'InstanceInterruptionBehavior': 'hibernate'|'stop'|'terminate'
}
Use them sparingly as each behaviour has some pros and cons, e.g. you must take care of process network connection interruption if yo use hibernate. For stop, you may want to store data into another mounted EBS.
answered Nov 22 '18 at 8:23
mootmootmootmoot
6,38622037
Can I change the instance type from one time to persistent without terminating the spot instance?
– Rynardt
Nov 22 '18 at 9:27
1
@Rynardt Well, you didn't see the option inside AWS Console, it means it is not changeable at the moment.
– mootmoot
Nov 22 '18 at 9:44
add a comment |
According to boto3 Spot instance creation documentation, you may also instruct the instance to stop or hibernate if you set the instance type to persistent. The default behaviour is terminate. This features is added in November 2017.
response = client.request_spot_fleet(
SpotFleetRequestConfig={
.....
Type='one-time'|'persistent',
'InstanceInterruptionBehavior': 'hibernate'|'stop'|'terminate'
}
Use them sparingly as each behaviour has some pros and cons, e.g. you must take care of process network connection interruption if yo use hibernate. For stop, you may want to store data into another mounted EBS.
answered Nov 22 '18 at 8:23
mootmootmootmoot
6,38622037
Can I change the instance type from one time to persistent without terminating the spot instance?
– Rynardt
Nov 22 '18 at 9:27
1
@Rynardt Well, you didn't see the option inside AWS Console, it means it is not changeable at the moment.
– mootmoot
Nov 22 '18 at 9:44
add a comment |
According to boto3 Spot instance creation documentation, you may also instruct the instance to stop or hibernate if you set the instance type to persistent. The default behaviour is terminate. This features is added in November 2017.
response = client.request_spot_fleet(
SpotFleetRequestConfig={
.....
Type='one-time'|'persistent',
'InstanceInterruptionBehavior': 'hibernate'|'stop'|'terminate'
}
Use them sparingly as each behaviour has some pros and cons, e.g. you must take care of process network connection interruption if yo use hibernate. For stop, you may want to store data into another mounted EBS.
answered Nov 22 '18 at 8:23
mootmootmootmoot
6,38622037
According to boto3 Spot instance creation documentation, you may also instruct the instance to stop or hibernate if you set the instance type to persistent. The default behaviour is terminate. This features is added in November 2017.
response = client.request_spot_fleet(
SpotFleetRequestConfig={
.....
Type='one-time'|'persistent',
'InstanceInterruptionBehavior': 'hibernate'|'stop'|'terminate'
}
Use them sparingly as each behaviour has some pros and cons, e.g. you must take care of process network connection interruption if yo use hibernate. For stop, you may want to store data into another mounted EBS.
answered Nov 22 '18 at 8:23
mootmootmootmoot
6,38622037
edited Nov 22 '18 at 8:28
answered Nov 22 '18 at 8:23
mootmootmootmoot
6,38622037
answered Nov 22 '18 at 8:23
mootmootmootmoot
6,38622037
answered Nov 22 '18 at 8:23
mootmootmootmoot
6,38622037
6,38622037
Can I change the instance type from one time to persistent without terminating the spot instance?
– Rynardt
Nov 22 '18 at 9:27
1
@Rynardt Well, you didn't see the option inside AWS Console, it means it is not changeable at the moment.
– mootmoot
Nov 22 '18 at 9:44
add a comment |
Can I change the instance type from one time to persistent without terminating the spot instance?
– Rynardt
Nov 22 '18 at 9:27
1
@Rynardt Well, you didn't see the option inside AWS Console, it means it is not changeable at the moment.
– mootmoot
Nov 22 '18 at 9:44
Can I change the instance type from one time to persistent without terminating the spot instance?
– Rynardt
Nov 22 '18 at 9:27
Can I change the instance type from one time to persistent without terminating the spot instance?
– Rynardt
Nov 22 '18 at 9:27
1
1
@Rynardt Well, you didn't see the option inside AWS Console, it means it is not changeable at the moment.
– mootmoot
Nov 22 '18 at 9:44
@Rynardt Well, you didn't see the option inside AWS Console, it means it is not changeable at the moment.
– mootmoot
Nov 22 '18 at 9:44
add a comment |
For setting the interruption behavior to stop, we need to take care of some requirements:
- For a Spot Instance request, the type must be persistent, not
one-time. You cannot specify a launch group in the Spot Instance
request. - For a Spot Fleet request, the type must be maintain, not request.
- The root volume must be an EBS volume, not an instance store volume.
by following the above requirements, we can change the interruption behavior from terminate to stop.
Please refer the following url for reference:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html
answered Nov 22 '18 at 8:54
Dharmesh PurohitDharmesh Purohit
963
My Spot Instance request is currently one-time and not persistent. How do I change it without terminating the running instance?
– Rynardt
Nov 22 '18 at 9:26
add a comment |
For setting the interruption behavior to stop, we need to take care of some requirements:
- For a Spot Instance request, the type must be persistent, not
one-time. You cannot specify a launch group in the Spot Instance
request. - For a Spot Fleet request, the type must be maintain, not request.
- The root volume must be an EBS volume, not an instance store volume.
by following the above requirements, we can change the interruption behavior from terminate to stop.
Please refer the following url for reference:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html
answered Nov 22 '18 at 8:54
Dharmesh PurohitDharmesh Purohit
963
My Spot Instance request is currently one-time and not persistent. How do I change it without terminating the running instance?
– Rynardt
Nov 22 '18 at 9:26
add a comment |
For setting the interruption behavior to stop, we need to take care of some requirements:
- For a Spot Instance request, the type must be persistent, not
one-time. You cannot specify a launch group in the Spot Instance
request. - For a Spot Fleet request, the type must be maintain, not request.
- The root volume must be an EBS volume, not an instance store volume.
by following the above requirements, we can change the interruption behavior from terminate to stop.
Please refer the following url for reference:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html
answered Nov 22 '18 at 8:54
Dharmesh PurohitDharmesh Purohit
963
For setting the interruption behavior to stop, we need to take care of some requirements:
- For a Spot Instance request, the type must be persistent, not
one-time. You cannot specify a launch group in the Spot Instance
request. - For a Spot Fleet request, the type must be maintain, not request.
- The root volume must be an EBS volume, not an instance store volume.
by following the above requirements, we can change the interruption behavior from terminate to stop.
Please refer the following url for reference:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html
answered Nov 22 '18 at 8:54
Dharmesh PurohitDharmesh Purohit
963
answered Nov 22 '18 at 8:54
Dharmesh PurohitDharmesh Purohit
963
answered Nov 22 '18 at 8:54
Dharmesh PurohitDharmesh Purohit
963
answered Nov 22 '18 at 8:54
Dharmesh PurohitDharmesh Purohit
963
963
My Spot Instance request is currently one-time and not persistent. How do I change it without terminating the running instance?
– Rynardt
Nov 22 '18 at 9:26
add a comment |
My Spot Instance request is currently one-time and not persistent. How do I change it without terminating the running instance?
– Rynardt
Nov 22 '18 at 9:26
My Spot Instance request is currently one-time and not persistent. How do I change it without terminating the running instance?
– Rynardt
Nov 22 '18 at 9:26
My Spot Instance request is currently one-time and not persistent. How do I change it without terminating the running instance?
– Rynardt
Nov 22 '18 at 9:26
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53425796%2fchange-interruption-behavior-of-fulfilled-aws-spot-request%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
