This set of Templates provide all the components to deploy a single Gerrit master in ECS
Two templates are provided in this example:
cf-cluster
: define the ECS cluster and the networking stackcf-service
: defined the service stack running Gerritcf-dns-route
: defined the DNS routing for the serviceerror_log
is exported in a Log Group in CloudWatchAs a prerequisite to run this stack, you will need a registered and correctly configured domain in Route53.
Once you will have it you can continue with the next steps:
aws ec2 create-key-pair --key-name gerrit-cluster-keys
NOTE: the EC2 key pair are useful when you need to connect to the EC2 instances for troubleshooting purposes. Store them in a pem
file to use when ssh-ing into your instances as follow: ssh -i yourKeyPairs.pem <ec2_instance_ip>
make create-all
make delete-all
The above commands for the creation and deletion of the stacks use a set of default parameters which can be overridden as in the following example:
make create-all CLUSTER_STACK_NAME=my-cluster-stack SERVICE_STACK_NAME=my-service-stack
Keep in mind, that once you override a parameter in the creation of the stack, you will have to do the same in the deletion, i.e.:
make delete-all CLUSTER_STACK_NAME=my-cluster-stack SERVICE_STACK_NAME=my-service-stack
This is the list of the parameters:
CLUSTER_STACK_NAME
: name of the cluster stack. gerrit-cluster
by default.SERVICE_STACK_NAME
: name of the service stack. gerrit-service
by default.DNS_ROUTING_STACK_NAME
: name of the DNS routing stack. gerrit-dns-routing
by default.HOSTED_ZONE_NAME
: name of the hosted zone. mycompany.com
by default.SUBDOMAIN
: name of the sub domain. gerrit-master-demo
by default.You Gerrit instance will be available at this URL: http://<HOSTED_ZONE_NAME>.<SUBDOMAIN>
.
The available ports are 8080
for HTTP and 29418
for SSH.