launch-ec2.sh

#!/bin/bash
# launch an EC2 server and install application
set -x
# this script runs on a machine where "Universal Command Line Interface for Amazon Web Services"
# https://github.com/aws/aws-cli is installed and is authenticated to amazon web services

# like a russia doll, this script 
#    -   creates a script that runs as root on a brand new amazon linux ec2 
#    -   creates a script that runs as the 'aspace' unix role account that installs archives space

set -eu
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" # http://stackoverflow.com/questions/59895
. $DIR/setenv.sh
cd $DIR
# make these parameters; not stuff read from setenv.sh
echo "$DB_INSTANCE_IDENTIFIER $TAG $EC2_SIZE $RDS_SIZE"

# poor man's templates; hard coded parameters
hackconf() {	
  sed -e "s,%{DB_URL},$2," -e "s,%{TAG},$3,g" -e "s,%{PW1},$4," -e "s,%{PW2},$5," $1.template.sh > $1
}

# figure out database connection string to put in confing/config.rb
password=`cat ~/.ec2/.dbpass`

# see if the database is up
# "jq is like sed for JSON" data http://stedolan.github.com/jq/
endpoint=`aws --region $EC2_REGION rds describe-db-instances --db-instance-identifier $DB_INSTANCE_IDENTIFIER | jq .DBInstances[0].Endpoint.Address -r`
echo $endpoint
if [ "$endpoint" != 'null' ]
  then
    echo "$endpoint" is already running
    echo "Do you want to start an EC2 still?"
    select yn in "Yes" "No"; do # http://stackoverflow.com/a/226724/1763984
        case $yn in
            Yes ) break;;
            No ) exit;;
        esac
    done
  else
    # launch the database
    aws --region $EC2_REGION rds create-db-instance \
      --db-instance-identifier $DB_INSTANCE_IDENTIFIER \
      --db-instance-class $RDS_SIZE \
      --db-parameter-group-name utf8  \
      --engine MySQL                  \
      --db-name archivesspace         \
      --master-user-password $password  \
      --port 3306                     \
      --backup-retention-period 1     \
      --allocated-storage 10          \
      --master-username aspace        \
      --publicly-accessible           \
      --availability-zone $ZONE
fi

# wait for the database to spin up if needed
while [ "$endpoint" == 'null' -o -z "$endpoint" ]
  do
  sleep 15 
  echo "."
  endpoint=`aws --region $EC2_REGION rds describe-db-instances --db-instance-identifier $DB_INSTANCE_IDENTIFIER | jq .DBInstances[0].Endpoint.Address -r`
  done

db_url="jdbc:mysql://$endpoint:3306/archivesspace?user=aspace\&password=$password\&useUnicode=true\&characterEncoding=UTF-8"
#                                                            ^ escaped & as \& for regex ...

# make sure we have an endpoint
if [ -z "$endpoint" ]; then		# not sure why set -u is not catching this
  echo "no endpoint, did you run launch-rds.sh?"
  exit 1
fi

# start user-data script payload
# https://help.ubuntu.com/community/CloudInit
cat > aws_init.sh << DELIM
#!/bin/bash
set -eux
# this gets run as root on the amazon machine when it boots up

# install packages we need from amazon's repo
yum -y update			# get the latest security updates

## system configuration
# redirect port 8080 to port 80 so we don't have to run tomcat as root
# http://forum.slicehost.com/index.php?p=/discussion/2497/iptables-redirect-port-80-to-port-8080/p1
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080
chkconfig sendmail off

# install the rest of the software we need
# git is needed for the build
yum -y install git 
# ant gives us better java
yum -y install ant 

# if we run the jar file; we need daemonize
yum -y install http://fr2.rpmfind.net/linux/dag/redhat/el5/en/x86_64/dag/RPMS/daemonize-1.6.0-1.el5.rf.x86_64.rpm
# yum -y install ftp://rpmfind.net/linux/dag/redhat/el5/en/i386/dag/RPMS/daemonize-1.6.0-1.el5.rf.i386.rpm

# twincat tomcat setup needs xsltproc for server.xml template
yum install -y libxslt

# these aren't strictly necessary for the application but will be usful for debugging

# iotop is a handy utility on linux
easy_install pip
pip install http://guichaz.free.fr/iotop/files/iotop-0.4.4.tar.gz

# _   /|  ack is a tool like grep, optimized for programmers
# \'o.O'  http://betterthangrep.com
# =(___)=
#    U    ack!
curl http://betterthangrep.com/ack-standalone > /usr/local/bin/ack && chmod 0755 /usr/local/bin/ack


DELIM

# only on the t1.micro, tune swap
if [ "$EC2_SIZE" == 't1.micro' ]; then
  cat >> aws_init.sh << DELIM
# t1.micro's don't come with any swap; let's add 1G
## to do -- add test for micro
# http://cloudstory.in/2012/02/adding-swap-space-to-amazon-ec2-linux-micro-instance-to-increase-the-performance/
# http://www.matb33.me/2012/05/03/wordpress-on-ec2-micro.html
/bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024
/sbin/mkswap /var/swap.1
/sbin/swapon /var/swap.1
# in case we get rebooted, add swap to fstab
cat >> /etc/fstab << FSTAB
/var/swap.1 swap swap defaults 0 0
FSTAB
# t1.micro memory optimizations
DELIM

fi

cat >> aws_init.sh << DELIM
# create role account for the application
useradd aspace

# move the application home directory onto the bigger disk if it is there
if [ -e /media/ephemeral0 ]; then
  # remember this is just session storage, this is just for creating a test server
  mv /home/aspace /media/ephemeral0/aspace
  ln -s /media/ephemeral0/aspace /home/aspace
fi

# install public keys for operator accounts
su - ec2-user -c 'curl https://raw.github.com/tingletech/aws-as/master/public-keys >> ~/.ssh/authorized_keys'


# create script to setup the role account and set permissions
touch ~aspace/init.sh
chown aspace:aspace ~aspace/init.sh
chmod 700 ~aspace/init.sh
# write the file
cat > ~aspace/init.sh <<EOSETUP
DELIM
# as_role_account.sh is created from as_role_account.sh.template.sh
# it is run as the aspace role account on the target machine 
# a poor sed based template system is used (switch to better perl oneliner)
# to hack sensitive info into the script
hackconf as_role_account.sh $db_url $TAG `uuidgen` `uuidgen`
# cat the script into the payload
cat as_role_account.sh >> aws_init.sh 

# finish off the user-data payload file
cat >> aws_init.sh << DELIM
EOSETUP
# init.sh will have passwords, it should be removed if it runs; leave for debugging if it fails
su - aspace -c ~aspace/init.sh
rm ~aspace/init.sh 
## chkconfig an init.d script that will start and stop monit
DELIM
# back to the local machine

gzip aws_init.sh
base64 aws_init.sh.gz > aws_init.sh.gz.base64
# clean up
rm as_role_account.sh 

command="aws --region $EC2_REGION ec2 run-instances 
     --min-count 1                                   
     --image-id $AMI_EBS                             
     --max-count 1                                   
     --user-data file:aws_init.sh.gz.base64                 
     --key-name ec2-keypair                          
     --monitoring file:monitoring.json
     --instance-type $EC2_SIZE                       
     --placement file:placement.json"

echo "ec2 launch command"

# launch an ec2 and grab the instance id
instance=`$command | jq '.Instances[0] | .InstanceId' -r`

# wait for the new ec2 machine to get its hostname
hostname=`aws ec2 describe-instances --instance-ids $instance | jq ' .Reservations[0] | .Instances[0] | .PublicDnsName'` 
echo "instance started, waiting for hostname"
while [ "$hostname" == '""' -o -z "$hostname" -o "$hostname" == 'null' ]
  do
  sleep 15
  echo "."
  hostname=`aws ec2 describe-instances --instance-ids $instance | jq ' .Reservations[0] | .Instances[0] | .PublicDnsName'` 
  done

echo $hostname

# clean up
rm aws_init.sh.gz
rm aws_init.sh.gz.base64