#awscloud #awscli #aws #vimaldaga #righteducation #educationredefine #rightmentor #worldrecordholder #linuxworld #makingindiafutureready #righeudcation #awsbylw #arthbylw
5.The final step is to attach the above created EBS volume to the instance created in the previous steps.
To use AWS CLI, we need to download and install it on the top of Operating System with which we are working. So, after installing to check whether its successfully installed, use the command:
aws --version
Here, we need to add the Access-key and Secret-key provided by AWS while creating this IAM User. Also, along with this we need to mention the default output format and the region. Here, region I am using is Mumbai i.e. ap-south-1.
So, now creating a keypair : --key-name is an option to give a name to our key.
Now, we have our keypair ready and we can see that on the console too. 'taskkey' is created successfully.
A security group acts as a virtual firewall for your instance to control inbound and outbound traffic. When you create a security group, you specify a friendly name of your choice. You can have a security group for use in EC2-Classic with the same name as a security group for use in a VPC. However, you can't have two security groups for use in EC2-Classic with the same name or two security groups for use in a VPC with the same name.Now, for creating a security group.
Now, lets create an EC2 instance. This instance will have the keypair and security groups attached that we created just now.
Our instance is now launched in ap-south-1a.
Now, we will create a 1 GB Volume using EBS. EBS comes under the EC2 service of AWS.The volume type will be general purpose SSD Volume:
Our EBS volume is now created and ready. This volume we need to attach to the EC2 instance we have created earlier.
Our volume is now successfully attached and we can see that in the Console of AWS:
