Amazon has started offering a year free trial: Ihttp://aws.amazon.com/free.
So I'm trying to get my first instance ever running on ec2. I'm trying to use the x86-64 ami from https://fedoraproject.org/wiki/Cloud_SIG/EC2_Images.
But:
/opt/amazon/webservices/ec2-api-tools-1.3-57419/bin/ec2-run-instances ami-e291668b -k pstam-keypair Client.InvalidParameterValue: The requested instance type's architecture (i386) does not match the architecture in the manifest for ami-e291668b (x86_64)
Supposedly the Micro instance in the free trial supports both 32 and 64 bit:
Micro Instance
613 MB memory Up to 2 EC2 Compute Units (for short periodic bursts) EBS storage only 32-bit or 64-bit platform I/O Performance: Low API name: t1.micro
I tried:
/opt/amazon/webservices/ec2-api-tools-1.3-57419/bin/ec2-run-instances ami-e291668b -t t1.micro -k pstam-keypair Client.UnsupportedOperation: AMIs with an instance-store root device are not supported for the instance type 't1.micro'.
The 386 ami works.
Am I doing something wrong, or does F14 64-bit image just not work as a micro instance?
sean
On Sun, Nov 7, 2010 at 1:23 PM, sean darcy seandarcy2@gmail.com wrote:
Amazon has started offering a year free trial: Ihttp://aws.amazon.com/free.
So I'm trying to get my first instance ever running on ec2. I'm trying to use the x86-64 ami from https://fedoraproject.org/wiki/Cloud_SIG/EC2_Images.
But:
/opt/amazon/webservices/ec2-api-tools-1.3-57419/bin/ec2-run-instances ami-e291668b -k pstam-keypair Client.InvalidParameterValue: The requested instance type's architecture (i386) does not match the architecture in the manifest for ami-e291668b (x86_64)
Supposedly the Micro instance in the free trial supports both 32 and 64 bit:
Micro Instance
613 MB memory Up to 2 EC2 Compute Units (for short periodic bursts) EBS storage only 32-bit or 64-bit platform I/O Performance: Low API name: t1.micro
I tried:
/opt/amazon/webservices/ec2-api-tools-1.3-57419/bin/ec2-run-instances ami-e291668b -t t1.micro -k pstam-keypair Client.UnsupportedOperation: AMIs with an instance-store root device are not supported for the instance type 't1.micro'.
The 386 ami works.
Am I doing something wrong, or does F14 64-bit image just not work as a micro instance?
sean
Well it appears that the 32 bit image doesn't work either as a micro instance! Is this a result of the images being "instance-store" rather than EBS backed images? Whatever that means.
AFAICS, none of the the F14 images work under the free tier :-(
sean
On 11/7/2010 16:12, sean darcy wrote:
Well it appears that the 32 bit image doesn't work either as a micro instance! Is this a result of the images being "instance-store" rather than EBS backed images? Whatever that means.
Yes. You will need to create or wait for a EBS-backed image first.
On 2010-11-07, at 23:12, sean darcy wrote:
Well it appears that the 32 bit image doesn't work either as a micro instance! Is this a result of the images being "instance-store" rather than EBS backed images? Whatever that means.
You can read more about differences for example here:
http://www.magpiebrain.com/2010/07/19/aws-s3-vs-ebs-backed-instances/
And EBS is explained here:
HTH
--Marek
On Sun, Nov 7, 2010 at 2:12 PM, sean darcy seandarcy2@gmail.com wrote:
On Sun, Nov 7, 2010 at 1:23 PM, sean darcy seandarcy2@gmail.com wrote:
Amazon has started offering a year free trial: Ihttp://
aws.amazon.com/free.
(snip)
Supposedly the Micro instance in the free trial supports both 32 and 64
bit:
Just to clarify - the 32bit/64bit part has nothing to do with what is not working. Amazon has two options for the mounted filesystems; EBS, and S3. They made a decision for some reason that the micro size would only be available to EBS-backed AMIs - which is odd, considering that a micro should be the most throw-away, and ebs is more permanent than S3. The Fedora AMIs are currently only available as S3-backed images. Those will be converted to EBS soon, however - at which point you'll be able to use the micro instances with the official Fedora AMIs.
Does that makes sense? The error message you got gave this answer, but was cryptic - and we can't really get in the business of helping construct ec2-run-instances commands, and interpreting the results - that's a bit outside the scope of the group, I'd think (you'd have the same result if you were running that command on a solaris workstation, to build an ubuntu instances; it's not Fedora on the Cloud-related). You should try euca2ools anyway, works better ;)
Brian LaMere