Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  • Elastic beanstalk - We currently have three environments deployed to Tomcat 7.x
    • Repository Services - The main Synapse REST API.
    • Authentication Services - The REST API for Authentication.
    • Portal - The main Synapse Web site.
  • RDS - All transactional Synapse meta data is store stored in a MySQL database.
  • CloudSearch - Search and Query features are currently supported by cloudsearch
  • SNS - All database alarms are currently configured to send emails to the development team.

...

  1. Administration level AWS account access key and secret key.
  2. You will need an S3 bucket named: '${stack}-default'.
    1. This bucket should contain the property file with all of your stack's passwords named '${stack}-default.properties
  3. SSL Certificates used for the Elastic Load Balancer must be placed in the S3 bucket named: '${stack}-default'. The following files must be there:
    1. SSL/gd_bundle.crt (from GoDaddy)
    2. SSL/gd_intermediatesagebase.org.crt (from GoDaddy)
    3. SSL/sagebase.org.crtprivate-key-for-ssl-certs-2048.pem (from /work/platform/PasswordsAndCredentials/SshCertificates)

Building a Stack

...

Get the Code

The first step is to get the Synapse-Stack-Builder jar either from Artifactory or cloning from GitHub.  To clone from GitHub:

...

There is a minimum amount of configuration information that you must provide to the stack builder.  This is done by passing Java properties file path the path to a java Properties file to the stack builder.  To setup this file start by making a copy of the following file:

...

Code Block
./build-stack.sh <config.properties_file_path>

You may receive errors when you run the stack builder for the first time.  That is because it takes time to ready RDS and ElasticBeanstalk instances.  Run it again when the instances are ready to get rid of the errors.

CNAME Setup

Currently, there is one extra step need to get the stack ready (we hope to automate this step soon).  To access the new stack you will need to create some CNAMEs in GoDaddy:

HostPoints ToExample
auth-${stack}-${instance}auth-${stack}-${instance}-sagebase-org.elasticbeanstalk.comauth-dev-hill -> auth-dev-hill-sagebase-org.elasticbeanstalk.com
repo-${stack}-${instance}repo-${stack}-${instance}-sagebase-org.elasticbeanstalk.comrepo-dev-hill -> repo-dev-hill-sagebase-org.elasticbeanstalk.com
portal-${stack}-${instance}portal-${stack}-${instance}-sagebase-org.elasticbeanstalk.comportal-dev-hill -> portal-dev-hill-sagebase-org.elasticbeanstalk.com
search-${stack}-${instance}search-${stack}-${instance}-sagebase-org.elasticbeanstalk.comsearch-dev-hill -> search-dev-hill-sagebase-org.elasticbeanstalk.com