commit | 46ad8a38bfe1700a986306b3e9f2fa99deba83cd | [log] [tgz] |
---|---|---|
author | Fabio Ponciroli <ponch78@gmail.com> | Mon Mar 09 18:36:30 2020 +0100 |
committer | Fabio Ponciroli <ponch78@gmail.com> | Fri Mar 13 09:58:47 2020 +0100 |
tree | 850f2c98bba1ac236364cfe7fb08a9b369c22f90 | |
parent | 6b24b5b4e57c12a4b76a6b94e9fe7adae9e3fb0c [diff] |
CF template for single Gerrit master in ECS CF to deploy a single Gerrit master with ECS. The configuration is currently using the standard Gerrit Docker image with default configuration. We still need to: - define an entry in Route53 with the URL for the Gerrit cluster - persist volumes with the repositories content - forward logs to CloudWatch - define a proper health check - enable SSL termination for HTTP - allow custom Gerrit configuration Feature: Issue 12445 Change-Id: I038817ad5210106a45c94ceb45c82422fe7f6324
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.