Amazon EC2

icon picker
Amazon Machine Images(AMIs)

An Amazon Machine Image (AMI) is a critical component in AWS that provides the necessary information to launch EC2 instances.
Here are the main components and features of AMIs:

Components of an AMI

Template for the Root Volume
Includes the operating system, application server, and applications.
Defines the initial state of the instance when launched.
Launch Permissions
Controls which AWS accounts can use the AMI to launch instances.
Can be shared with specific AWS accounts or made public for all AWS users.
Block Device Mapping
Specifies the volumes to attach to the instance when it’s launched.
Defines the storage devices (e.g., EBS volumes or instance store volumes) that will be available to the instance.

AMI Regional Availability

Regional Scope: AMIs are specific to the region where they are stored. You can only launch an instance from an AMI within the same region.
Cross-Region Copy: AMIs can be copied to other regions using the AWS Management Console, AWS CLI, or AWS API. This allows for geographical flexibility and disaster recovery planning.

Volume Types Attached to Instances

Amazon Elastic Block Store (EBS)
Persistent Storage: EBS volumes are persistent, meaning the data remains even after the instance is stopped or terminated.
Snapshots: EBS snapshots are used to back up the data, stored in Amazon S3.
Benefits: Durable, scalable, and suitable for applications requiring high availability and data persistence.
Instance Store Volumes
Ephemeral Storage: Instance store volumes are temporary storage, meaning data is lost if the instance is stopped or terminated.
Usage: Useful for temporary storage of information that changes frequently, such as buffers, caches, and scratch data.
Creation: A template stored on Amazon S3 is used to create the volume when the instance is launched.

Key Points

Creating AMIs: You can create custom AMIs by configuring an instance to your requirements and then creating an AMI from that instance.
Using AMIs: AMIs simplify the process of setting up multiple instances with the same configuration, ensuring consistency and efficiency.
Sharing AMIs: Share custom AMIs with other AWS accounts or the community to allow others to use your configurations.
Lifecycle Management: Regularly update and manage your AMIs to incorporate the latest patches, updates, and configuration changes.
Custom AMIs are built for a specific region not global.
Custom AMI take space and they live in Amazon S3.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.