快照和AMI之间的AWS区别 [英] 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.
这篇关于快照和AMI之间的AWS区别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
