Skip to main content

AWS AMIs

 AMIs 

Amazon Web Services (AWS) publishes many Amazon Machine Images (AMIs) that contain common software configurations for public use. In addition, members of the AWS developer community have published their own custom AMIs. You can also create your own custom AMI or AMIs; doing so enables you to quickly and easily start new instances that have everything you need. For example, if your application is a website or a web service, your AMI could include a web server, the associated static content, and the code for the dynamic pages. As a result, after you launch an instance from this AMI, your web server starts, and your application is ready to accept requests.

All AMIs are categorized as either backed by Amazon EBS, which means that the root device for an instance launched from the AMI is an Amazon EBS volume, or backed by instance store, which means that the root device for an instance launched from the AMI is an instance store volume created from a template stored in Amazon S3.

The description of an AMI indicates the type of root device (either ebs or instance store). This is important because there are significant differences in what you can do with each type of AMI. For more information about these differences, see Storage for the root device (p. 102).

You can deregister an AMI when you have finished using it. After you deregister an AMI, you can't use it to launch new instances. Existing instances launched from the AMI are not affected. Therefore, if you are also finished with the instances launched from these AMIs, you should terminate them


Comments

Popular posts from this blog

Terraform Commands

  Terraform Cheat Sheet terraform version $ terraform version Terraform v1.0.1 on darwin_amd64 terraform init $ terraform init Ask for input if necessary. If false, will error if input was required. $ terraform init -input=false You can also change the backend details using  -backend-config  option.,  reconfigure  will reconfigure the backend, ignoring any saved configuration . $ terraform init -backend-config=PATH/TO/CONFIGURATION_FILE -reconfigure