From: Cédric Jeanneret [mailto:firstname.lastname@example.org]
Sent: Thursday, 31 January 2013 5:22 PM
Subject: Re: Instance-store Amazon AMI
Oh, I see. Yes, right we can add them through the AWS Console. Fact
do not want to create our own AMI anymore, so I don't think I'll
code and recreate the AMI ;).
I just have to find out whether this can be done in our
(CFN) templates - pretty sure Amazon thought about it.
It may be just good to add some warning regarding the lack of
ephemeral storage on either the wiki page (btw, registered AMI on
are wrong :/ ) or amazon marketplace. If I have some nice CFN stuff,
post it in here - just have to see with my work team if this
solution is suitable
Thanks a lot for your work and your answer.
On 2013-01-31 10:10, Anders Ingemann wrote:
> Actually, I used to do that by default
> ) but removed that feature because you now can mount them
> in AWS when starting an instance. The problem is that you will
> some invalid default mappings when starting instances. In order
> this to work with all instance types, I have to map every
> instance store, which isn't very pretty. You can simply re-add the
> code in the above link to map all instance stores (keep in mind we
> euca2ools instead of ec2-tools now) or possibly write a plugin for
> On 31 January 2013 09:50, Cédric Jeanneret <email@example.com>
>> The Debian provided AMI are only EBS based, which is a bit
>> no ephemeral storage are attached by default. For example,
>> an m1.small instance based on the provided AMI should get a 150G
>> ephemeral storage under /dev/xvdb - but there's nothing at all
>> Would it be possible to provide "Instance store" AMI, as those
>> will have the default ephemeral storage?
>> Thanks a lot for you answers.
>> To UNSUBSCRIBE, email to firstname.lastname@example.org
>> with a subject of "unsubscribe". Trouble? Contact
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact