Menu Close

Month: February 2015 (page 1 of 3)

Stopping Vs. Terminating Instances: What’s the Difference?

Being in complete control is one of the many characteristics of AWS EC2 instances. Since there are many types of instances, this post will put the spotlight on EBS-backed AMIs.

  • To know if you are using an EBS-backed instance, go to EC2 Dashboard > Images > AMIs. If the value of the root device shows ebs, then it’s EBS-backed.

The nature of EBS-backed AMIs like AMIMOTO AMI is that you can stop, start and terminate it anytime.

 

To stop or to terminate? What’s the difference?  

Though it’s the most frequently asked question, it’s also the one of the most crucial ones. In this post, we will compare the two.

02 copy

At the EC2 Dashboard running instances menu, you can find the options “Terminate” and “Stop”. Gear up first before hitting that button.

 

Stopping the Instance 

What happens to the instance? 

Root:

If you stop an instance, root volume is preserved (EBS volume is not deleted) and other devices that are attached to the instance keep on running.

Modification:

Once the Instance State shows “stopped,”  you have the ability to set the conditions you would like for it. This is also the time when you may change the instance type. Whether to scale up or down is entirely up to you.

When it’s at stopped mode, you can fix some system issues and do some updates, change the user data, RAM disk and kernel. These attributes may only be changed if the instance has been stopped.

 

Can I restart the instance again? 

Yes. After clicking start, Instance State will show “pending”, and you know it’s ready when it shows “running”.

During the instance’s pending state, AWS will move the instance to a new host computer, so the data in RAM of the previous host computer will be lost.

 

Do I get billed?

No:

  • usage per hour
  • data transfer fees

Yes:

  • storage fees (EBS volume)
  • every time you restart a stopped instance, you get charged for a full hour (even you will do this once or many times within one hour)
  • for an unmapped IP (unless you associate the IP with an instance)

 

What happens to my IP address? 

EC2 VPC:

  • Your private IP remains the same (so the EIP linked with the private IP is still connected with the instance)
  • Gets a new public instance only if you don’t have an EIP

EC2 Classic:

  • You get a new public and private IP when the instance is restarted (so the EIP previously linked with the private IP is no longer associated with the instance)

AMIMOTO PVM and AMIMOTO HVM are only Linux/Unix, (2014.03) Amazon Linux-based instances. However, if you stop and start a Windows instance, the host name of that instance is changed to match a new IP address.

 

Why stop an instance? 

  • cannot perform an instance status check
  • doesn’t run applications well
  • to scale up or down
  • to modify user data, kernel, RAM

You only stop an instance just to start it again. Stopping an instance for the purpose of saving is not the option. You might want to consider terminating the instance instead.

 instance_lifecycle

Instance Lifecycle (AWS Documentation)

Terminating the Instance 

What happens to the instance? 

Root:

The root and other devices attached to the instance when launched will all be deleted automatically. By default, the root volume is deleted following the termination.

Modification:

You cannot modify or connect to a terminated instance.

 

Can I restart the instance again? 

No, but you can always create a new one and even launch an additional instance using the same AMI.

 

Do I get billed?

No. Once the Instance State shows “shutting down” and “terminated” you stop getting billed.

On Free Tier, you do not get charged when you terminate an instance and create a new micro instance.

 

What happens to my IP? 

The EIP associated to your instance will be disassociated.

 

Why terminate an instance? 

You have decided that you no longer need it.

After you terminate an instance, you can still see it at the EC2 Dashboard, but this console entry will be deleted later on.

 

How to Launch Concrete5 HVM Instances with 1-Click

To celebrate today’s launch of Concrete5 HVM by DigitalCube at the AWS Marketplace, we have done a series of posts about this first release.

Related article: Official Launch Concrete5 HVM 

 

There are a couple of ways on how to launch Concrete5 HVM:

Launch Concrete5 HVM Instances Manually and doing it in 1-Click, which is the easiest and fastest way. Prior to doing so, login to Amazon Web Services and search for Concrete5 HVM by DigitalCube.

 

Choose a region.

01

Review and Launch with 1-Click. 

02

Concrete5 pricing is hourly or annually. For the smallest instance, t2.micro, the estimate cost per month* is about USD $27 assuming a 24-hour usage for a duration of 30 days.

*Total cost varies on region, instance size, volume, added services, etc.

That’s it. 

03

View your Concrete5 HVM instance at the AWS Management Console. Once you see the “Status Checks” (from Initializing to) running, that’s it. It’s ready for use.

Here are other documentation and resources for Concrete5 HVM:

You may also find Concrete5 HVM at Amiage’s official site. 

How to Launch Concrete5 HVM Instances Manually

A while ago, we’ve published our post on “Official Launch: Concrete5 HVM”. Concrete5 is an interesting open source CMS where we provide high performance hosting service that we’ve just freshly released at the AWS Marketplace today.

This documentation will show you how to launch an HVM instance of Concrete5 manually. If you are an AMIMOTO AMI user, you will notice that creating an Amimoto instance is similar to launching Concrete5 instance, with minor differences.

Before proceeding, login to your Amazon Web Services Account.

Instance Launch 

  1. Choose a region where you would like to launch your Concrete5 HVM instance and click EC2. 

01

2. Once you’re at the EC2 Dashboard, click Launch Instance. 

02

 

3. Select AWS Marketplace > type “Concrete5 HVM” > Choose Concrete5 (HVM) DigitalCube.

03

 

4. Details of Concrete5 HVM will appear, including the hourly rates for N. California region. Please note that this is the rate of N. California at the time of writing. If you have selected another region, the prices may be different.

After reviewing the details, click Continue. 

04

 

5. It’s time to choose an instance type. If you have a new AWS account, you are entitled to a free tier on the smallest instance of t2.micro. This instance type is for blogs, company sites, etc. with page views of 100,000 or more.

After instance selection, click > Configure Instance Details. 

05

 

6. Here is where you can set up your Concrete5 HVM instance. You can configure how many instances you would like to launch, set the network, and so on.

Click > Add Storage. 

06

 

7. The storage option that we use here is EBS. At the time of writing, the maximum capacity of EBS is 16TB. It stores about 5 Million+ HD images, 272 thousand hours of music, and over 4 thousand movies. This is its size for now, and it might be even more in the future.

In this step, you can add additional EBS volumes to your Concrete5 HVM instance. When you do so, it can be used as any other physical hard drive. 

Click > Tag Instance. 

07

 

8. Give your Concrete5 HVM instance a name. This is very helpful and even avoids confusion when you have more than one instance.

Select > Configure Security Group 

08

 

9. You may edit the settings of the Security Group here.

Next > Review and Launch 

09

 

10. If you are happy and sure about the instance settings, click > Launch.

To edit and go back, click > Previous

10

 

11. This time, we have to create a new key pair.

“Public–key cryptography uses a public key to encrypt a piece of data, such as a password, then the recipient uses the private key to decrypt the data. The public and private keys are known as a key pair.”

Give your key pair a nameDownload Key Pair Launch Instances 

11

 

12. Launching takes 3-5 seconds, and when it’s ready, View Instances 

12

Elastic IP Address

13. You will see here all the details of your Concrete5 HVM instance. You may give it a static IP address by clicking Elastic IPs.

13

 

14. Allocate New Address 

14
15
16
 

15. Choose your running Concrete5 HVM instance > Associate

18

 

16. Go to Instances > copy your Public IP address > Paste to your browser 

19

 

Enjoy! 

17. Login to Concrete5 and enjoy!

21

 

One More Thing

When you install Concrete5, you will see this:

Install C5 - Github

This post is an additional documentation about Concrete5. You can also view our resources like the one we have on GitHub and Concrete5’s Homepage.

Visit DigitalCube’s Concrete5 HVM at the AWS Marketplace for more details on pricing and specifications. If you are in need of further support, get in touch with us. 

© 2017 DigitalCube Blog. All rights reserved.

Theme by Anders Norén.