| commit | bb8e4a904807063da2c662c8a09a6d5f853ff60a | [log] [tgz] |
|---|---|---|
| author | Antonio Barone <syntonyze@gmail.com> | Mon Mar 08 16:35:09 2021 +0100 |
| committer | Antonio Barone <syntonyze@gmail.com> | Tue Mar 09 10:39:11 2021 +0000 |
| tree | eb01b593ce258485521660ee773b12821eeaf8a3 | |
| parent | 510bd94565e494291fc239354454af02796b7a5d [diff] |
Stop creating useless network stacks for primary-replica When network resources are NOT provided via the setup.env file then a new VPC is created with its related components, such as subnets and IGW. However, when network resources ARE provided externally via the setup.env file, then the network stack doesn't do much except returning the provided input values as output, for other stacks to consume. This causes the creation of an empty stack, with no resources created, but just outputs. Prevent the creation of empty network stacks by checking the existence of VPC related input parameters and skip the creation of the stack, when they are defined. Change-Id: I7e360875036b46bce3816ddefa658466669f5fc0
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
To manipulate aws cloudformation outputs jq
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.