AWS Utilization Monitor build & deploy guidelines

The AWS Utilization Monitor is a RESTful service that scans AWS accounts for all used resources and generates a statistic for it. To get stats about several accounts you either change the AWS credentials file or deploy this service to each AWS account you want to monitor and collect data via its RESTful API.

This project shows everything necessary, to deploy a fully working Java Spring web application to Amazon EC2 with the help of Docker and Senza (stups.io).

Requirements

• JDK 8
• Maven 3
• Docker (see Boot2Docker for Mac users)
• STUPS Senza (https://github.com/zalando-stups/senza)
• AWS account

Make sure stups / senza is up-to-date

$ sudo apt-get install python3 python3-pip
$ sudo easy_install-3.4 pip

$ sudo pip3 install --upgrade stups
$ sudo pip3 install --upgrade stups-senza
$ sudo pip3 install --upgrade stups-piu
$ sudo pip3 install --upgrade stups-mai
$ sudo pip3 install --upgrade zign
$ sudo pip3 install --upgrade httpie-zign

$ export LC_ALL=en_US.utf-8
$ export LANG=en_US.utf-8

Prepare docker when using boot2docker on MacOS

$ $(boot2docker shellinit)    

Login to AWS

$ mai

Login to Pier One Docker registry

$ pierone login

Build the project

$ mvn clean package
$ docker build -t %YOUR_DOCKER_REGISTRY%/aws-utilization-monitor:1.0 .

Run locally

$ java -jar target/aws-utilization-monitor.jar
$ java -javaagent:newrelic/newrelic.jar -jar -Dconnection.components.s3.details=false target/aws-utilization-monitor.jar

Check that our Docker image works

$ docker run -p 8080:8080 -it %YOUR_DOCKER_REGISTRY%/aws-utilization-monitor:1.0

Visit http://localhost:8080/! Stop your server with Ctrl+C.

Deploy it in the cloud!

$ docker push %YOUR_DOCKER_REGISTRY%/aws-utilization-monitor:1.0

If you did not set up Senza before, go and visit Stups docs: https://docs.stups.io

Initialize your new application:

$ senza init aws-utilization-monitor.yaml --region eu-west-1

Add our Docker image as a new version to our application:

$ senza create aws-utilization-monitor.yaml 1 1.0 --region eu-west-1

This step might take a long(tm) time (minutes). Afterwards you will be able to directly go to your deployed version: https://aws-utilization-monitor-1.0.%YOUR_DOMAIN%/

The application's main domain will still not show the deployed version. Now you can switch traffic of your main domain to the new version:

$ minion version traffic aws-utilization-monitor 1.0 100

Have fun with https://aws-utilization-monitor.%YOUR_DOMAIN%/!

$ aws-utilization-monitor.%YOUR_DOMAIN%

Observe your logs (remember that the Load Balancer checks spam your HTTP):

$ senza console myapp.yaml