Amazon Machine Image (AMI)
AMI is a template which can create a copy of the instances in AWS. We can specify an AMI when we launch an instance, and we can launch as many instances from the AMI as per the need. AMI will help to automate the scaling function of the cloud.
Here in this lab we are creating an AMI images of the webserver and queueserver and testing them.
For creating the AIM I went to AWS EC2 console, right click the web server instance and choose ‘Image - Create Image’
Given a name and reference for the image for identification,
Then I have repeated the same steps to create a copy of 'Queue server'
Now we have to test the copies, for that, I have launched an instance by right-clicking on the AMI instance.
I have selected the AIM role as same as the webserver's role so that this instance will get the same permissions as the original server.
Here I am selecting the security group same as the original server for getting the same rules(HTTP and RDP).
Then selected the same key as the web server, this will be used for login to the instance.
To ensure the AMI working, I have used the public DNS of the original server and it showed me the private IP of my original webserver in the web server.
Then I used the new instance's DNS to open the DinoStore, Then it showed the private IP of the new machine.
Here in this lab we are creating an AMI images of the webserver and queueserver and testing them.
For creating the AIM I went to AWS EC2 console, right click the web server instance and choose ‘Image - Create Image’
Given a name and reference for the image for identification,
Then I have repeated the same steps to create a copy of 'Queue server'
Now we have to test the copies, for that, I have launched an instance by right-clicking on the AMI instance.
I have selected the AIM role as same as the webserver's role so that this instance will get the same permissions as the original server.
Here I am selecting the security group same as the original server for getting the same rules(HTTP and RDP).
Then selected the same key as the web server, this will be used for login to the instance.
To ensure the AMI working, I have used the public DNS of the original server and it showed me the private IP of my original webserver in the web server.
Then I used the new instance's DNS to open the DinoStore, Then it showed the private IP of the new machine.
No comments:
Post a Comment