Should a detached EBS volume keep charging monthly?
up vote
8
down vote
favorite
First of all, I'm not very used to AWS nor DevOps/admin stuff, but want to learn. So I set up an EC2 instance and attached an EBS volume (15 Gb) some months ago, for testing something during a few days.
Then I realize that the monthly charge was full (EC2 + EBS) because I left the instance active, so I detached the volume and stopped the instance and EC2 instance did not charge anymore.
But now, I see that EBS volume is still charging 1.5 USD/month, even when it is detached. Should I delete the volume to avoid any charge? or there is any sort of stop or disable for volumes?
amazon-web-services amazon-ec2 amazon-ebs
New contributor
add a comment |
up vote
8
down vote
favorite
First of all, I'm not very used to AWS nor DevOps/admin stuff, but want to learn. So I set up an EC2 instance and attached an EBS volume (15 Gb) some months ago, for testing something during a few days.
Then I realize that the monthly charge was full (EC2 + EBS) because I left the instance active, so I detached the volume and stopped the instance and EC2 instance did not charge anymore.
But now, I see that EBS volume is still charging 1.5 USD/month, even when it is detached. Should I delete the volume to avoid any charge? or there is any sort of stop or disable for volumes?
amazon-web-services amazon-ec2 amazon-ebs
New contributor
1
Unrelated, but to future visitors: If you have had trouble understanding what exactly each AWS service was, I found this post highly helpful: expeditedssl.com/aws-in-plain-english
– I.Am.A.Guy
Nov 21 at 16:42
add a comment |
up vote
8
down vote
favorite
up vote
8
down vote
favorite
First of all, I'm not very used to AWS nor DevOps/admin stuff, but want to learn. So I set up an EC2 instance and attached an EBS volume (15 Gb) some months ago, for testing something during a few days.
Then I realize that the monthly charge was full (EC2 + EBS) because I left the instance active, so I detached the volume and stopped the instance and EC2 instance did not charge anymore.
But now, I see that EBS volume is still charging 1.5 USD/month, even when it is detached. Should I delete the volume to avoid any charge? or there is any sort of stop or disable for volumes?
amazon-web-services amazon-ec2 amazon-ebs
New contributor
First of all, I'm not very used to AWS nor DevOps/admin stuff, but want to learn. So I set up an EC2 instance and attached an EBS volume (15 Gb) some months ago, for testing something during a few days.
Then I realize that the monthly charge was full (EC2 + EBS) because I left the instance active, so I detached the volume and stopped the instance and EC2 instance did not charge anymore.
But now, I see that EBS volume is still charging 1.5 USD/month, even when it is detached. Should I delete the volume to avoid any charge? or there is any sort of stop or disable for volumes?
amazon-web-services amazon-ec2 amazon-ebs
amazon-web-services amazon-ec2 amazon-ebs
New contributor
New contributor
New contributor
asked Nov 21 at 12:48
gustavovelascoh
1434
1434
New contributor
New contributor
1
Unrelated, but to future visitors: If you have had trouble understanding what exactly each AWS service was, I found this post highly helpful: expeditedssl.com/aws-in-plain-english
– I.Am.A.Guy
Nov 21 at 16:42
add a comment |
1
Unrelated, but to future visitors: If you have had trouble understanding what exactly each AWS service was, I found this post highly helpful: expeditedssl.com/aws-in-plain-english
– I.Am.A.Guy
Nov 21 at 16:42
1
1
Unrelated, but to future visitors: If you have had trouble understanding what exactly each AWS service was, I found this post highly helpful: expeditedssl.com/aws-in-plain-english
– I.Am.A.Guy
Nov 21 at 16:42
Unrelated, but to future visitors: If you have had trouble understanding what exactly each AWS service was, I found this post highly helpful: expeditedssl.com/aws-in-plain-english
– I.Am.A.Guy
Nov 21 at 16:42
add a comment |
3 Answers
3
active
oldest
votes
up vote
12
down vote
accepted
In addition to the other answer, you can take a Snapshot of the volume, which stores the data in S3, a cheaper storage option. You can then restore the snapshot to an EBS volume in the future when you want to access the disk.
See Amazon EC2 terminology - AMI vs. EBS vs. Snapshot vs. Volume for more info on the specifics.
You can simply right-click the EBS volume in the AWS Web Console, and then click "Create Snapshot". After this snapshot is created, you can delete the EBS volume. Of course, I'd test restoring the snapshot and using the restored volume before deleting your EBS volume for good.
1
Thanks, That's a good option.
– gustavovelascoh
Nov 21 at 14:23
add a comment |
up vote
18
down vote
You're always charged for EBS volumes because that data is occupying space on physical storage somewhere, even if it is not attached to a running instance.
Thanks, I supposed that.
– gustavovelascoh
Nov 21 at 14:22
add a comment |
up vote
5
down vote
Should I delete the volume to avoid any charge? or there is any sort of stop or disable for volumes?
There is a delete on termination flag for the attached EBS volumes
If this is set, when the instance is terminated the associated EBS volume is destroyed
You can set this flag when setting up a EC2 in the console or can use the aws ec2 modify-instance-attribute
CLI command
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
12
down vote
accepted
In addition to the other answer, you can take a Snapshot of the volume, which stores the data in S3, a cheaper storage option. You can then restore the snapshot to an EBS volume in the future when you want to access the disk.
See Amazon EC2 terminology - AMI vs. EBS vs. Snapshot vs. Volume for more info on the specifics.
You can simply right-click the EBS volume in the AWS Web Console, and then click "Create Snapshot". After this snapshot is created, you can delete the EBS volume. Of course, I'd test restoring the snapshot and using the restored volume before deleting your EBS volume for good.
1
Thanks, That's a good option.
– gustavovelascoh
Nov 21 at 14:23
add a comment |
up vote
12
down vote
accepted
In addition to the other answer, you can take a Snapshot of the volume, which stores the data in S3, a cheaper storage option. You can then restore the snapshot to an EBS volume in the future when you want to access the disk.
See Amazon EC2 terminology - AMI vs. EBS vs. Snapshot vs. Volume for more info on the specifics.
You can simply right-click the EBS volume in the AWS Web Console, and then click "Create Snapshot". After this snapshot is created, you can delete the EBS volume. Of course, I'd test restoring the snapshot and using the restored volume before deleting your EBS volume for good.
1
Thanks, That's a good option.
– gustavovelascoh
Nov 21 at 14:23
add a comment |
up vote
12
down vote
accepted
up vote
12
down vote
accepted
In addition to the other answer, you can take a Snapshot of the volume, which stores the data in S3, a cheaper storage option. You can then restore the snapshot to an EBS volume in the future when you want to access the disk.
See Amazon EC2 terminology - AMI vs. EBS vs. Snapshot vs. Volume for more info on the specifics.
You can simply right-click the EBS volume in the AWS Web Console, and then click "Create Snapshot". After this snapshot is created, you can delete the EBS volume. Of course, I'd test restoring the snapshot and using the restored volume before deleting your EBS volume for good.
In addition to the other answer, you can take a Snapshot of the volume, which stores the data in S3, a cheaper storage option. You can then restore the snapshot to an EBS volume in the future when you want to access the disk.
See Amazon EC2 terminology - AMI vs. EBS vs. Snapshot vs. Volume for more info on the specifics.
You can simply right-click the EBS volume in the AWS Web Console, and then click "Create Snapshot". After this snapshot is created, you can delete the EBS volume. Of course, I'd test restoring the snapshot and using the restored volume before deleting your EBS volume for good.
edited Nov 23 at 8:02
ivan_pozdeev
306413
306413
answered Nov 21 at 13:49
zymhan
1,0601929
1,0601929
1
Thanks, That's a good option.
– gustavovelascoh
Nov 21 at 14:23
add a comment |
1
Thanks, That's a good option.
– gustavovelascoh
Nov 21 at 14:23
1
1
Thanks, That's a good option.
– gustavovelascoh
Nov 21 at 14:23
Thanks, That's a good option.
– gustavovelascoh
Nov 21 at 14:23
add a comment |
up vote
18
down vote
You're always charged for EBS volumes because that data is occupying space on physical storage somewhere, even if it is not attached to a running instance.
Thanks, I supposed that.
– gustavovelascoh
Nov 21 at 14:22
add a comment |
up vote
18
down vote
You're always charged for EBS volumes because that data is occupying space on physical storage somewhere, even if it is not attached to a running instance.
Thanks, I supposed that.
– gustavovelascoh
Nov 21 at 14:22
add a comment |
up vote
18
down vote
up vote
18
down vote
You're always charged for EBS volumes because that data is occupying space on physical storage somewhere, even if it is not attached to a running instance.
You're always charged for EBS volumes because that data is occupying space on physical storage somewhere, even if it is not attached to a running instance.
answered Nov 21 at 13:07
Michael Hampton♦
162k26299613
162k26299613
Thanks, I supposed that.
– gustavovelascoh
Nov 21 at 14:22
add a comment |
Thanks, I supposed that.
– gustavovelascoh
Nov 21 at 14:22
Thanks, I supposed that.
– gustavovelascoh
Nov 21 at 14:22
Thanks, I supposed that.
– gustavovelascoh
Nov 21 at 14:22
add a comment |
up vote
5
down vote
Should I delete the volume to avoid any charge? or there is any sort of stop or disable for volumes?
There is a delete on termination flag for the attached EBS volumes
If this is set, when the instance is terminated the associated EBS volume is destroyed
You can set this flag when setting up a EC2 in the console or can use the aws ec2 modify-instance-attribute
CLI command
add a comment |
up vote
5
down vote
Should I delete the volume to avoid any charge? or there is any sort of stop or disable for volumes?
There is a delete on termination flag for the attached EBS volumes
If this is set, when the instance is terminated the associated EBS volume is destroyed
You can set this flag when setting up a EC2 in the console or can use the aws ec2 modify-instance-attribute
CLI command
add a comment |
up vote
5
down vote
up vote
5
down vote
Should I delete the volume to avoid any charge? or there is any sort of stop or disable for volumes?
There is a delete on termination flag for the attached EBS volumes
If this is set, when the instance is terminated the associated EBS volume is destroyed
You can set this flag when setting up a EC2 in the console or can use the aws ec2 modify-instance-attribute
CLI command
Should I delete the volume to avoid any charge? or there is any sort of stop or disable for volumes?
There is a delete on termination flag for the attached EBS volumes
If this is set, when the instance is terminated the associated EBS volume is destroyed
You can set this flag when setting up a EC2 in the console or can use the aws ec2 modify-instance-attribute
CLI command
answered Nov 22 at 9:11
Vorsprung
1636
1636
add a comment |
add a comment |
gustavovelascoh is a new contributor. Be nice, and check out our Code of Conduct.
gustavovelascoh is a new contributor. Be nice, and check out our Code of Conduct.
gustavovelascoh is a new contributor. Be nice, and check out our Code of Conduct.
gustavovelascoh is a new contributor. Be nice, and check out our Code of Conduct.
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%2fserverfault.com%2fquestions%2f941051%2fshould-a-detached-ebs-volume-keep-charging-monthly%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
1
Unrelated, but to future visitors: If you have had trouble understanding what exactly each AWS service was, I found this post highly helpful: expeditedssl.com/aws-in-plain-english
– I.Am.A.Guy
Nov 21 at 16:42