|author||Antonio Barone <firstname.lastname@example.org>||Fri Oct 30 14:09:43 2020 +0100|
|committer||Antonio Barone <email@example.com>||Mon Nov 02 10:30:06 2020 +0100|
Make ha-proxy highly available A single ha-proxy instance is a single point of failure. Set ha-proxy to a minimum of 2 instances, for achieving high-availability of the proxy layer. Bug: Issue 13609 Change-Id: I0d8661666ad82e89e7b9d41a66e9b31b66db932d
Those are a collection of AWS CloudFormation templates and scripts to deploy Gerrit in AWS.
The aim is to provide some guidelines and example on how to deploy different Gerrit setups in the Cloud using AWS as provider.
The goal of Gerrit AWS Templates is to provide fully-functional Gerrit installations to helps users deploying Gerrit on AWS by providing out-of-the-box templates.
With Gerrit AWS Templates, developers and administrator can create a production-ready installation on the cloud in minutes and in a repeatable way, allowing them to focus on fine tuning of the Gerrit configuration to suit the user needs.
The provided CloudFormation templates automate the entire creation and deployment of the infrastructure and the application.
To manage your AWS services via command line you will need to install AWS CLI and set it up to point to your account.
To build gerrit and related-components' images Docker
This is a list of external services that you might need to setup your stack and some suggestions on how to easily create them.
If you need to setup a SMTP service Amazon Simple Email Service can be used. Details how setup Amazon SES can be found here.
To correctly setup email notifications Gerrit requires ssl protocol on default port 465 to be enabled on SMTP Server. It is possible to setup Gerrit to talk to standard SMTP port 25 but by default all EC2 instances are blocking it. To enable port 25 please follow this link.
If you need a testing LDAP server you can find details on how to easily create one in the LDAP folder.