From the course: AWS Essential Training for Architects (2019)

Creating a custom AMI - Amazon Web Services (AWS) Tutorial

From the course: AWS Essential Training for Architects (2019)

Start my 1-month free trial

Creating a custom AMI

“

- [Instructor] Now that we have created an easy two instance and configured it exactly as needed to play the role of a web server in the application architecture and have it successfully connecting to an RDS database. An Amazon machine image or AMI should be created from it. This AMI will then be used to easily recreate the instance as many times as needed across multiple availability zones. Amazon EC2 provides a number of tools to facilitate the creation of AMIs including the AWS Management Console. So here, I've logged into the console in the browser and AMIs are part of the EC2 service. So again, we could search for the service or we could go to our recently visited services, EC2. In this case, I want to go to the running server from which I want to create the AMI so I'll go here. I only have one so far. I've already selected that server and I can choose up here in actions, image, create image. The instance ID is already chosen for us based on the instance that we're creating an image for. I can create a name so I'll give it demo web server, we'll call it 1.0. The image description, initial web server image and we have the option to create the image without rebooting the instance. And if at all possible, it's recommended to allow the instance to reboot when making an image. It will ensure a more consistent snapshot. The tool tips actually indicate as much if you hover over that. But in the event that a reboot cannot happen, its production system and it just can't be an option, you do have the option to create the image with it with no reboot. In our case, we can reboot the server with this image creation so leaving that unchecked is fine. We don't need to anything else with the volumes. This all looks good so from here, I can just create the image. So it's indicating that the image creation has been received and it's working on creating that image. So an image of the server is now being created. I can go over here, look at AMIs and we can see it's in progress right now. The status, again, will go through several life cycle states. Currently it's in pending. It won't be able to be used until it's available so we'll need to wait on this AMI to complete before we can use it. Great, didn't take too long. It's a pretty small server so the image was pretty quick to create. It's now in an available status. So now we can use it to create new web tier instances and now we can also use it to configure auto scaling to take better advantage of the Clouds elastic nature.

Contents