| commit | 966f519975a4ee067d9306213063f6ab3a4f3abd | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Wed May 20 11:41:43 2020 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Wed May 20 11:41:43 2020 +0100 |
| tree | 68366369483cdabd5d5898113c67d6f64fc2d231 | |
| parent | 9be4829f0bf5bb62a112e8df41158d6d9d66ceca [diff] |
Define a global AWS_PREFIX to allow isolating resources Define a global variable in the makefine.env included by all receipes so that it is possible to define a prefix to be used for all the resources created by the makefiles and templates. This avoids the manual find and replace of the 'gerrit-' prefix inside each one of the setups in the receipes. Change-Id: I34e268eed601766863883e4bfdcac497927c62d0
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.