|
t1.micro instance defaults to 1024 GB storage after use of AMI copy feature
Posted on:
Dec 16, 2013 8:07 AM
|
|
|
|
 |
This question is not answered. Answer it to earn points.
|
In April, I used this script to build a Tor Cloud image for us-east-1, based on an official Ubuntu image. Once the image was registered and published on AWS, I used the AMI copy feature to copy this image to the other regions.
Any instances created based on the image in us-east-1 will default to 4 GB of storage space. Any instances created based on the same, copied image in any of the other other regions will default to 1024 GB of storage space.
AWS Support said the images not in us-east-1 had been configured to use 1024 GB of storage space. I am not sure how that could have happened, given that the original image in us-east-1 is correct. I wonder if something might have gone wrong in the process of copying the image to the other regions?
|
|
|
|
Re: t1.micro instance defaults to 1024 GB storage after use of AMI copy feature
Posted on:
Dec 16, 2013 12:34 PM
|
|
|
|
Hello,
I was able to check the script, and did not see any issue there as it does create a 4 GB
volume and not a 1024 GB. I'll investigate the copy process to make sure there is not a bug there.
Regards,
Mike P.
|
|
|
|
Re: t1.micro instance defaults to 1024 GB storage after use of AMI copy feature
Posted on:
Dec 16, 2013 2:59 PM
|
|
|
|
Hello,
I was able to create new AMI from a running TOR instance launched
from (ami-11af6d78) and copy the new AMI to each region via the EC2 console.
I was not able to duplicate the issue you have observed.
Did you instead use the AWS CLI to perform the copy ? If so which version ?
Is there a specific AMI you'd like me to retest with ?
Regards,
Mike P.
|
|
|
|
Re: t1.micro instance defaults to 1024 GB storage after use of AMI copy feature
Posted on:
Dec 16, 2013 4:34 PM
|
|
|
|
Hey Mike,
I used AMI copy from the AWS Management Console (note that this was back in April). If you would like to retest, try building an image for us-east-1, copy it to us-west-1 using AMI copy within the console, and then spin up an instance of the us-west-1 image.
As an example, here are three AMI IDs for images with a default 1024 GB of storage space: ami-18ecc05d, ami-d09403e0, ami-20011554.
Thanks,
Runa
Edited by: runasand on Dec 16, 2013 4:34 PM
|
|
|
|
Re: t1.micro instance defaults to 1024 GB storage after use of AMI copy feature
Posted on:
Dec 17, 2013 11:56 AM
|
|
|
|
Hello,
I have also attempted to reproduce your issue and see that I have a 1TB default root volume when launching the AMI created in us-east-1 from us-west-1. Would you be able to run the following command on an instance you launch in us-west-1 with the AMI you created.
fdisk -l
This should let us know if you need to resize the volume as it may not be utilizing the full 1TB, which may be the reason you are only seeing 4GB on the instance.
Regards,
Howard K.
|
|
|
|
Re: t1.micro instance defaults to 1024 GB storage after use of AMI copy feature
Posted on:
Dec 17, 2013 5:12 PM
|
|
|
|
#1: Below is the output of fdisk -l on an AMI created in us-east-1 and launched in us-east-1 with 4 GB default storage:
Disk /dev/xvda1: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders, total 8388608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/xvda1 doesn't contain a valid partition table
#2: Below is the output of fdisk -l on an AMI created in us-east-1 and launched in us-west-1 with 1024 GB default storage:
Disk /dev/xvda1: 1099.5 GB, 1099511627776 bytes
255 heads, 63 sectors/track, 133674 cylinders, total 2147483648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/xvda1 doesn't contain a valid partition table
|
|
|
|
Re: t1.micro instance defaults to 1024 GB storage after use of AMI copy feature
Posted on:
Dec 22, 2013 3:45 PM
|
|
|
|
Hello Runa,
I'll build a new image and test as you suggested. I'll also check the AMIs you listed.
When I check the snapshot properties for those AMIs I do see 4GB.
Thank you for your patience while I investigate this.
Regards,
Mike P.
|
|
|
|
Re: t1.micro instance defaults to 1024 GB storage after use of AMI copy feature
Posted on:
Dec 28, 2013 4:36 PM
|
|
|
|
Hello Runa,
I was able to build a new AMI using the script and copy it to other regions
without an issue. However I didi note on the public AMIs listed:
ami-18ecc05d, ami-d09403e0, ami-20011554. That there are missing a 'default volume size'
The snapshot size the AMI has is indeed 4 GB, however the EC2 console is defaulting
to the 1024 GB EBS volume size since the AMI does not have a default size listed.
I will bring this to the attention of our console team for their consideration.
Thank you for bringing this to our attention.
Regards,
Mike P.
|
|
|
|
Re: t1.micro instance defaults to 1024 GB storage after use of AMI copy feature
Posted on:
Dec 31, 2013 7:30 AM
|
|
|
|
Hi,
Could you please try to re-copy the images which are missing their size from the original image.
Alternatively, when launching via the console you can specify the size of the root device that you want.
-Vinay
|
|
|
|
|
