AWS 快照和 AMI 之间的区别 [英] AWS Difference between a snapshot and AMI
问题描述
所以我很难弄清楚这两者之间的区别.
So I am having trouble working out what, specifically is the difference between these two.
据我所知，快照只是磁盘驱动器的备份，而 AMI 是整个系统(或我应该说的实例)的备份，但从技术上讲，整个系统并不是完全位于磁盘上驾驶?如果是这样，那么就没有明显的区别，我遗漏了什么?
As I understand it, a snapshot is simply a backup of the disk drive, whereas the AMI is a backup of the entire system (or instance I should say), but isn't the entire system technically wholly located on the disk drive? and if that's the case then there is no clear difference and I am missing something?
推荐答案
AMI 有两种类型(和对应的实例):
There are two types of AMIs (and corresponding instances):
instance-store(有时称为基于 S3 的).这些不太常见，我不建议初学者使用它们.实例存储 AMI 是根实例存储卷的副本加上一些元数据，全部以特殊格式保存在 S3 存储桶中
instance-store (sometimes called S3-based). These are less common and I don't recommend them for beginners. An instance-store AMI is a copy of the root instance-store volume plus some metadata, all saved in an S3 bucket in a special format
EBS 启动.这可能是您正在使用的.EBS 启动 AMI 是 EBS 根卷的 EBS 快照加上一些元数据，如架构、内核、AMI 名称、描述、块设备映射等.
EBS boot. This is probably what you are using. An EBS boot AMI is an EBS snapshot of the EBS root volume plus some metadata like the architecture, kernel, AMI name, description, block device mappings, and more.
您可以拍摄 EBS 启动卷的快照，并通过使用适当的元数据注册将其转换为 EBS 启动 AMI.其中最棘手的部分是指定正确的 AKI id(内核)，以便正确启动.
You can take a snapshot of an EBS boot volume and turn it into an EBS boot AMI by registering it with the appropriate metadata. The trickiest part of this is specifying the correct AKI id (kernel) so that it boots correctly.
这篇关于AWS 快照和 AMI 之间的区别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
