Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS: Stopping an Instance vs. Terminating an instance #29

Open
TheoFranquet opened this issue Nov 7, 2017 · 3 comments
Open

AWS: Stopping an Instance vs. Terminating an instance #29

TheoFranquet opened this issue Nov 7, 2017 · 3 comments

Comments

@TheoFranquet
Copy link

Hi,

Could someone clarify the difference between the two actions, and whether or not stopping an instance stops withdrawing money from my account (in the case of a c4.8xlarge).

Thanks

@lsc1234582
Copy link

Stopping an instance is shutting it down; terminating an instance destroys it altogether. You won't be billed for a stopped instance.

@guigzzz
Copy link

guigzzz commented Nov 7, 2017

From what I understand, if we had normal AWS accounts we would be billed (at least some) even for a stopped instance as it still reserves some disk space. However with AWS educate accounts, it seems we have 30GB of free EBS disk space to use, which means that we can have a number of stopped instances at a time. Could anyone confirm that what I have said is true.

@m8pple
Copy link
Contributor

m8pple commented Nov 8, 2017

The responses but @lsc1234582 and @guigzzz are correct, though to elaborate
a little:

Usually you would stop an instance if there is some kind of instance configuration or
data on the instance that you want to preserve. For example, if you are currently
debugging something but then have to go to a lecture, or sleep, or something else,
you might want to stop the instance now, then restart it again tomorrow. It saves
you the hassle of doing any configuration steps and cloning your work again.

Whenever you don't expect to use an instance again soon (e.g. within a day), it
is often better to terminate it. This has two benefits:

  • You won't be charged for any storage (though see below)
  • It forces you to transfer any data back and commit+push any changes you made
    If you come back to an instance after a week, it is very unlikely you remember exactly
    what is on it, so you can spend ages trying to resynchronise things. Better to
    make a conscious decision of what data you need to save while you still
    remember what the contents of the instance are, and whether they are important.

@guigzzz is correct that storage is billable - they currently charge $0.12 per GB-month
for EBS (Elastic Block Storage). So an 8GB instance costs ~$0.92 per month. But as
they point out, there is 30GB free EBS storage for you.

That 30GB is actually not part of AWS Educate, it actually applies to everyone in the
first 12 months of using AWS
. You can also
run a t2.micro instance permanently for the rest of the year for free if you want,
though watch out for the 15GB free data transfer limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants