Why custom AMI will always create snapshot?
Without the snapshot, there would be no way to create a reproducible, exact copy of the instance's storage that can launch instances from.
The snapshot ensure that you can later launch an identical instance from that AMI with the same OS, application, settings, and data.
Can I create my own AMI without snapshot?Is it possible?
It's not possible to create an AMI without a snapshot.
When you create a AMI from an EC2 instance, the underlying process involves capturing a snapshot of the instances EBS volume. These snapshot store the data and configuration of the volumes at the moment the AMI is created, which is critical for launching new instances from that AMI in the future.
How do you ensure the security of your AMIs?
AMIs often serve as the base image for launching EC2 instances. If an AMI is compromised or misconfigured, its could lead to vulnerabilities across all instances launched from it.
Always prefer using official AWS AMIs or trusted images from the AWS marketplace. These are regularly updated and patched.
How AMI's are stored and managed?
AMIs are stored and managed in AWS in a way that make it easy to create, use, and distribute custom machine images for EC2 instance.
The snapshots contain the EC2 instance OS, configuration, software, and data, which can be used to launch a new instances with the same setup.
How AMI's are stored and managed?
An AMI is a template stored as EBS snapshots with launch settings. These snapshots are saved in Amazon S3. AMIs are region specific, you can manage them using the AWS console or CLI. To save costs you can deregister the AMI and delete its snapshots.