Deploy microservices on AWS

[danielfc]

see #175

• gateway (public)
• insights (private)
• subtitles (private)
• jhipster-registry (private)

[danielfc]

Gateway
http://gateway-prod.us-east-1.elasticbeanstalk.com

Insights
http://insights-prod.us-east-1.elasticbeanstalk.com

Registry
http://registry-prod.us-east-1.elasticbeanstalk.com

Issues found along the way

• AWS EB requires the jar/war not to be executable. We configured it in each pom.xml in the prod profile.
• AWS EB works better with a RDS created from an environment instead of a separate RDS. This issue is more like a config thing in terms of Security Groups and stuff.
• Mongobee (migration for mongo) requires the property database in our application-prod.yml.
• JHipster JWT Secret. When using Microservices, we need to set the same secret for all applications including the registry. The property is JHIPSTER_SECURITY_AUTHENTICATION_JWT_SECRET.
• AWS EC2 Communication. Even though all instances are running in the same VPC, the Security Group by default accepts incoming only from port 80 -- we need to set port 8080 too, I guess.