Should a detached EBS volume keep charging monthly?











up vote
8
down vote

favorite
1












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?










share|improve this question







New contributor




gustavovelascoh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 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















up vote
8
down vote

favorite
1












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?










share|improve this question







New contributor




gustavovelascoh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 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













up vote
8
down vote

favorite
1









up vote
8
down vote

favorite
1






1





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?










share|improve this question







New contributor




gustavovelascoh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











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






share|improve this question







New contributor




gustavovelascoh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




gustavovelascoh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




gustavovelascoh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Nov 21 at 12:48









gustavovelascoh

1434




1434




New contributor




gustavovelascoh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





gustavovelascoh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






gustavovelascoh is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 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




    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










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.






share|improve this answer



















  • 1




    Thanks, That's a good option.
    – gustavovelascoh
    Nov 21 at 14:23


















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.






share|improve this answer





















  • Thanks, I supposed that.
    – gustavovelascoh
    Nov 21 at 14:22


















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






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "2"
    };
    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',
    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
    });


    }
    });






    gustavovelascoh is a new contributor. Be nice, and check out our Code of Conduct.










     

    draft saved


    draft discarded


















    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

























    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.






    share|improve this answer



















    • 1




      Thanks, That's a good option.
      – gustavovelascoh
      Nov 21 at 14:23















    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.






    share|improve this answer



















    • 1




      Thanks, That's a good option.
      – gustavovelascoh
      Nov 21 at 14:23













    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.






    share|improve this answer














    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.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    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














    • 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












    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.






    share|improve this answer





















    • Thanks, I supposed that.
      – gustavovelascoh
      Nov 21 at 14:22















    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.






    share|improve this answer





















    • Thanks, I supposed that.
      – gustavovelascoh
      Nov 21 at 14:22













    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.






    share|improve this answer












    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.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 21 at 13:07









    Michael Hampton

    162k26299613




    162k26299613












    • 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




    Thanks, I supposed that.
    – gustavovelascoh
    Nov 21 at 14:22










    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






    share|improve this answer

























      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






      share|improve this answer























        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






        share|improve this answer













        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







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 22 at 9:11









        Vorsprung

        1636




        1636






















            gustavovelascoh is a new contributor. Be nice, and check out our Code of Conduct.










             

            draft saved


            draft discarded


















            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.















             


            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            Plaza Victoria

            Puebla de Zaragoza

            Musa