Welcome to conjur-beanstalk

The beanstalk deployment template for conjur... in this repo we hope to provide a quick way to drop in and deploy Get Conjur into a beanstalk multi docker container... this repo is a work in progress so expect updates.

Steps to get setup

Get an AWS account and setup the beanstalk client Link to AWS docs or use our prebuilt beanstalk cli (in a docker container).

Using the Amazon EB CLI in Docker

1. Run bin/build-eb-image

   This will install Elastic Beanstalk's CLI in a clean Python environment and tag it as amazon-eb-cli

2. To use it:

   $ docker run --rm -it amazon-eb-cli -h
   usage: eb (sub-commands ...) [options ...] {arguments ...}
   
   Welcome to the Elastic Beanstalk Command Line Interface (EB CLI). 
   For more information on a specific command, type "eb {cmd} --help".
   

Clone this repo and initialize beanstalk

run eb init into the console to initialize your application/environment do this in the folder where you have cloned the repo

there are 2 files that you can use depending on the topology of your deployment: Single instance or MultiInstance

templates/MultiHost-RDS-Dockerrun.aws.json templates/SingleInstance-Dockerrun.aws.json

The default Dockerrun.aws.json provided is the MultiHost config, this will require the following:

1. setup an EBS environment with:

• load balancing (port 80 -> 8080)
• SSH (if you're into that sort of thing, helps to troubleshoot)
• RDS instance (something according to the use and size you want)
• security group modification to ensure it can talk to containers on port 8080

2. Rename the one you want to Dockerrun.aws.json then test or deploy.

3. to test locally: eb local run -v

4. to deploy: eb deploy

for more detailed info proceed to readme under the templates/ section

Notes The main difference between the two is basically whether you have a small deployment and a single instance of everything will do (pick SingleInstance-Dockerrun.aws.json), however if you want to scale out your environment in an N+1 fashion you can scale out the client/server component and drop the DB inside an RDS configuration and that will scale the DB vertically and then the app tier horizontally. This is probably an easier faster stop gap to deploying the clustered configuration which you may need for extremely highly available environments.

Helpful links:

• https://www.conjur.org

• https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-install.html

• https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker.html

• https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker_v2config.html

• https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker-eblocal.html