commit | 2cc2e44e445108a6340246ba09167b4bb0e75721 | [log] [tgz] |
---|---|---|
author | Luca Milanesio <luca.milanesio@gmail.com> | Tue May 19 16:49:59 2020 +0100 |
committer | Luca Milanesio <luca.milanesio@gmail.com> | Tue May 19 16:49:59 2020 +0100 |
tree | b9f32d7192c64066a8d71a2cd4039bfb5a204698 | |
parent | d3b49cd29af87fb8f677ad5631647f7f502ad752 [diff] | |
parent | 7cdbd25b1b20cb03abb378b2126e78e0e5526011 [diff] |
Merge branch 'stable-3.1' * stable-3.1: Make secrets generation idempotent Allow passing secrets prefix as an argument Do not update all packages on CentOS Do not install replication keys if setup not needed Add logic to control replication setup Use generic container.javaHome value Add SSH keys to AWS Secret Manager Change-Id: I7eaa95aabb27e0a0e1181e5ebe72c54167fc8196
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.