为什么我不能将AWS的新st1/sc1 EBS卷用作根卷 [英] Why can't I use the new st1/sc1 EBS volumes by AWS as root volumes

查看:259
本文介绍了为什么我不能将AWS的新st1/sc1 EBS卷用作根卷的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

AWS最近启动了sc1和st1 HDD EBS卷类型,在启动新的EC2实例或从已经创建的AMI启动时,我似乎无法将它们用作根卷.

AWS launched sc1 and st1 HDD EBS volume types recently, I can't seem to use these as root volumes while launching new EC2 instances or launching from already created AMI's (tried both).

我选择了一台m4机器,无论如何,根卷是EBS本身,下面是截图,我添加的第二个卷获得了新选项,但是第一个我不能选择相同的卷.这是特意为AWS的人吗?

I chose an m4 machine, in any case, the root volume is EBS itself, below is a screenshot, the second volume that I add gets the new options, however the first one I can't choose the same. Is this by design AWS people?

推荐答案

如果您从 http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html

表示

不能是启动卷

Cannot be a boot volume

及以下

吞吐量优化的HDD(st1)卷可提供低成本的磁性 根据吞吐量而不是性能定义性能的存储 IOPS.此卷类型非常适合大型顺序工作负载 例如Amazon EMR,ETL,数据仓库和日志处理. 可启动 不支持st1卷.

Throughput Optimized HDD (st1) volumes provide low-cost magnetic storage that defines performance in terms of throughput rather than IOPS. This volume type is a good fit for large, sequential workloads such as Amazon EMR, ETL, data warehouses, and log processing. Bootable st1 volumes are not supported.

冷HDD(sc1)卷提供了低成本的磁存储,该磁存储定义了 性能方面的吞吐量,而不是IOPS.用较低的 吞吐量限制比st1大,sc1非常适合大型, 顺序冷数据工作负载.如果您不需要经常访问 您的数据并希望节省成本,sc1提供了廉价 块存储. 不支持可启动sc1卷.

Cold HDD (sc1) volumes provide low-cost magnetic storage that defines performance in terms of throughput rather than IOPS. With a lower throughput limit than st1, sc1 is a good fit ideal for large, sequential cold-data workloads. If you require infrequent access to your data and are looking to save costs, sc1 provides inexpensive block storage. Bootable sc1 volumes are not supported.

这篇关于为什么我不能将AWS的新st1/sc1 EBS卷用作根卷的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆