This template describes a Jenkins master in a highly available manner. If the master instance fails it will be replaced automatically. All data stored on EFS where it is replicated across AZs and the file system can grow without a limit. The Jenkins master sits behind a load balancer to provide a fixed endpoint. Logs from the operating system and Jenkins are pushed to CloudWatch Logs.

1. This templates depends on one of our vpc-*azs.yaml templates. Launch Stack
2. Launch Stack
3. Click Next to proceed with the next step of the wizard.
4. Specify a name and all parameters for the stack.
5. Click Next to proceed with the next step of the wizard.
6. Click Next to skip the Options step of the wizard.
7. Check the I acknowledge that this template might cause AWS CloudFormation to create IAM resources. checkbox.
8. Click Create to start the creation of the stack.
9. Wait until the stack reaches the state CREATE_COMPLETE
10. Grab the URL of the Jenkins master from the Outputs tab of your stack.

• vpc/vpc-*azs.yaml (required)
• vpc/vpc-ssh-bastion.yaml
• security/auth-proxy-*.yaml

This template describes a Jenkins master in a highly available manner. If the master instance fails it will be replaced automatically. All data stored on EFS where it is replicated across AZs and the file system can grow without a limit. The Jenkins master sits behind a load balancer to provide a fixed endpoint. A dynamic pool of agents will execute builds. If the build queue grows new agents are provisioned. Of the build queue is empty agents are taken offline (only if they have no build running). System and Jenkins logs are pushed to CloudWatch Logs.

1. This templates depends on one of our vpc-*azs.yaml templates. Launch Stack
2. Launch Stack
3. Click Next to proceed with the next step of the wizard.
4. Specify a name and all parameters for the stack.
5. Click Next to proceed with the next step of the wizard.
6. Click Next to skip the Options step of the wizard.
7. Check the I acknowledge that this template might cause AWS CloudFormation to create IAM resources. checkbox.
8. Click Create to start the creation of the stack.
9. Wait until the stack reaches the state CREATE_COMPLETE
10. Grab the URL of the Jenkins master from the Outputs tab of your stack.

• vpc/vpc-*azs.yaml (required)
• vpc/vpc-ssh-bastion.yaml
• security/auth-proxy-*.yaml

We offer support for our CloudFormation templates: setting up environments based on our templates, adopting templates to specific use cases, resolving issues in production environments. Hire us!

We are looking forward to your feedback. Mail to team@widdix.de.

A cloudonaut.io project. Engineered by widdix.