aws cli run-instances block-device-mappings ephemeral encrypted

aws --version => aws-cli/1.1.1 Python/2.6.8 Linux/3.4.43-43.43.amzn1.x86_64

1. aws ec2 run-instances 
1. --image-id 
1. ami-eeff1122 
2. --instance-type 
1. m2.2xlarge 
3. --security-group-ids 
1. sg-eeff1122
4. --subnet-id 
1. subnet-eeff1122
5. --private-ip-address 
1. 10.0.0.2
6. --user-data 
1. file://meta_myserver.txt 
7. --block-device-mappings 
1. '[{ "DeviceName":"/dev/sdb", "VirtualName":"ephemeral0" }]'

For 50G EBS attached on boot (auto-deleted on terminate unless you override), block device mapping becomes:

1.  '[{ "DeviceName":"/dev/sdb", "VirtualName":"ephemeral0" },{"DeviceName":"/dev/sdc","Ebs":{"VolumeSize":50}}]'

WARNING: "Ebs" is very case sensitive here.

To encrypt the Ebs volume, add "Encrypted": true to the device params like so:

1.  {"DeviceName":"/dev/sdc","Ebs":{"VolumeSize":50,"Encrypted": true}}

Move huge directory on the root partition to a huge non-root parition

Assumption: /mnt is a huge disk partition separate from the / partition  (aka root partition)

1. mkdir -p /mnt/home/myfatdirectory
2. kill all processes that have open files to /home/myfatdirectory
1. lsof /home/myfatdirectory
2. make sure you get ZERO results, ie no processes have open files to this directory
3. mv /home/myfatdirectory /home/myfatdirectory_old 
4. mkdir -p /home/myfatdirectory
5. mount --bind /mnt/home/myfatdirectory /home/myfatdirectory
6. add to bottom of /etc/fstab, so the mount is picked up on reboot
1. /mnt/home/myfatdirectory /home/myfatdirectory none bind 0 0

NOTES:

1. fix perms as necessary by interleaving your own steps into the above
2. for the paranoid: you might want to make sure fstab entries work fine on reboot