harris2020ParticipantDec 11, 2020 at 2:52 am #654290
The first step is to create and register the AMI, which is then used to launch or set up AWS instances. Alternatively, you can launch instances from another AMI provided the AMI creator grants you with the necessary launch permissions. You can also copy an existing AMI within the same or different AWS region. Finally, you need to deregister an AMI once you no longer require it.
An AMI typically consists of the following three components:
The template that is the root volume for the AWS instances (example, application server, operating system, or web application).
Launch permissions that determine which AWS account can use this AMI to set up an instance.
Block device mapping that specifies the root device volumes that is attached to the AWS instance after launch.
What are the types of AWS AMI?
As an AWS user, you can choose your AMI on the basis of the following parameters:
You can choose an AMI on the basis of the supported operating system (or OS) like Windows or Linux.
32-bit or 64-bit architecture
This parameter is based on the architecture of your selected OS.
This parameter is based on the selected region of the Amazon machine image that comprises regions, availability zones, and local zones. Each region operates in different geographical regions and are independent of each other.
Storage (EBS or Instance store)
This AMI parameter is based on the storage of the root device. Based on storage, AMIs are categorized as either of the following two types namely:
EBS-backed instances: In this case, the root device for an AWS instance – launched using AMI – is an Amazon EBS volume that has been created from Amazon EBS.
Instance store-backed instances: In this case, the root device for an AWS instance – launched using Ami – is an Amazon instance store volume that has been created from an Amazon S3 template.
An AMI owner can determine their instance availability through the following three launch permissions:
Public, that grants instance launch permission to all AWS account holders.
Explicit, that grants launch permission only to specific AWS accounts.
Implicit, where only the AMI owner has the permission to launch an instance.
What are Shared AMIs?
In simple language, a shared AMI is one that an AWS developer creates and shares it with other users for use. Shared AMIs enable any new AWS user to easily get started with using the AWS platform. On the flip side, Shared AMIs are not guaranteed for any security or integrity and must be treated as any other foreign code.
You can locate the following shared AMIs from the Amazon EC2 console by selecting the “AMIs” option from the navigation pane:
Private images: that contains all the shared AMIs that are private and only for your se.
Public images: that contains all the shared AMIs that have been created for public use.
Additionally, you can also create your own AMI and share it for public use or with specific AWS accounts.
Here’s how you can share your AMI with all AWS account holders:
Open the Amazon EC2 console and choose AMIs from the navigation pane.
Select your AMI to be shared, then click Actions > Modify Image Permissions.
Select the “Public” option before saving your changes.
You must be logged in to reply to this topic.