This is the last post of AWS EC2 configuration. In this step we will add storage , tag instance and configure our security group.
As you see in the picture, first storage is your root volume. And the device name is /dev/sda1. It has initially 8 gb capacity but can be up to 1TB. It will be created from the snap-f88e3be6 snapshot that is stored in S3. There are two volume types for our storage. The standard volumes have average 100 IOPS ( like 7200 rpm device ) with burst capacity of up to hundreds of IOPS ( This is how your operating system creates more IOPS when it is booting up. For this reason the standard volumes are better for root devices ). The Provisioned IOPS volumes supports up to 4000 IOPS. And if you will use an application ( like database ) you should choose a provisioned iops volume type or also you can choose an EBS-optimized instance ( EBS optimized instances are directly attached to EBS volumes so the network usage is dedicated for them ). If you selected provisioned iops volume type, you should enter the number of iops needed. Finally if you don’t want your volume to be deleted when you terminate your instance , you should uncheck that option ( by default it is checked for your root volume ).
Next we can define our tags for our instance and so we can categorize our instances. For example we can use tags in our configuration management when configuring our salt states for specific instances.
By default a tag is defined that the key is “NAME” and for the value we can define “GOLLUM” . Also we can enter another tag like key is “Role” and the value is “development”.
The last step of configuring our instance is setting up a virtual firewall , security group.
By default aws creates a new security group for our instance, but of course we can assign our preconfigured security groups. In our example we will create a new one. First we give a name to our security group. And also it is important to use a good description. In the protocol selection we will configure which protocols we want our firewall to allow access to our instance. If it is a linux instance of course we want to use a ssh connection. By default it is selected as ssh ,the type is TCP and port range is 22. In the source section we can configure which ip addresses are allowed to use ssh. If we use 0.0.0.0/0 it means that all IP addresses are allowed to access that instance over that port. I you choose myip, aws automatically detects your public ip address. Another option is, of course, using a custom ip. For example you can allow http protocol ( tcp port 80 ) to everyone ( 0.0.0.0/0 ) but can allow custom http ( tcp port 8080 ) for your own ip adress for test purposes.
In the last step you review your settings and can launch your instance if everything is ok with your demands.