When you register the image, make sure to include an explicit
-a x86_64
Without this, you let the Black Box of Amazon's back end decide which architecture to use. Apparently it defaults to 32bit, or guessed wrong in your case.
To access the ephemeral (instance-store) storage Amazon includes with an EC2 instance, you need to define it when you launch an instance. Using the EC2 command line tools all you need to do is include the -b or --block-device-mapping option flag.
For example, this command would launch a single m1.large instance in us-east-1a, with ephemeral0 and ephemeral1 mapped to sdb1 and sdb2 respectively and the following options:
- ami-id
- (-n) number of instances to launch
- (-t) instance type
- (-z) availability zone
- (-b) block device mapping
- (-g) security group
- (-k) key name
-
ec2-run-instances ami-id -n 1 -t m1.large -z us-east-1a -b "/dev/sdb1=ephemeral0" -b "/dev/sdb2=ephemeral1" -g security_group -k key_name
Then you can format and mount the devices. (repeat each command once for each device)
sudo mkfs /dev/sdb[1..n]
sudo mkdir -p /media/ephemeral[0...n]
You can then either add the following two lines to your /etc/fstab (feel free to adjust your mount options, file system, etc.)
/dev/sdb1 /media/ephemeral0 auto defaults,comment=cloudconfig 0 2
/dev/sdb2 /media/ephemeral1 auto defaults,comment=cloudconfig 0 2
And mount the devices
sudo mount /media/ephemeral0
sudo mount /media/ephemeral1
Or, just mount the devices without adding these devices to the fstab file
sudo mount -t ext3 /dev/sdb1 /media/ephemeral0
sudo mount -t ext3 /dev/sdb2 /media/ephemeral1
Verify
df -h
Sample Output:
[ec2-user@ip-10-251-159-223 media]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 7.9G 883M 7.0G 12% /
tmpfs 3.7G 48K 3.7G 1% /dev/shm
/dev/xvdb1 414G 199M 393G 1% /media/ephemeral0
/dev/xvdb2 414G 199M 393G 1% /media/ephemeral1
[ec2-user@ip-10-251-159-223 media]$
By the way, once you customize your instance. Create your own AMI based on this instance and whenever you launch an instance from the resulting AMI the ephemeral storage will already be configured.
Also, take a look at the documentation provided on the AWS website.
Amazon Command Line Tools Documentation
Good Luck!
Best Answer
You list "1690 GB of instance storage". It isn't clear if you were just quoting the specs of your instance type or if you have actually formatted and are using all that storage.
It isn't clear from the question exactly what storage you want to increase. Here are some thoughts on different situations:
It is not possible to increase instance-store beyond the limit you quote. However, by default, that storage is not all formatted and mounted on the instance, so you could get up to that limit as long as you wanted to use instance-store. Be aware, that instance-store disk is ephemeral and the contents are lost when the instance is stopped, terminated, or fails.
If your instance itself is running on an instance-store root disk, then you cannot increase the size of the root disk without starting another instance, and even then, instance-store root disks have a hard limit of 10GB on EC2.
It is possible to create and attach EBS volumes to either instance-store or EBS boot instances if you simply want to add space and move your data there (recommended). It is also possible to increase the size of attached EBS volumes up to a limit of 1TB (and beyond using RAID0 of multiple EBS volumes).
All that said, I'm going to guess that the most likely situation you're in is that you are running an EBS boot instance and need to increase the size of the EBS boot volume.
You can increase the size of an EBS boot volume without control panel access (email/password for Amazon account), however you will need to have access to the AWS credentials in order to create snapshots and volumes, to detach and attach volumes, and to stop and start the instance. You will also need ssh access in order to resize the filesystem on the larger EBS volume.
Here's an article I wrote about this process:
In related topic to permissions, here's an article I wrote explaining the different types of AWS credentials:
Providing more details in your question about your situation and what you want to accomplish would help improve the relevance of the answers.