This repository contains Azure ARM templates to install the following Atlassian Data Center products:
- Bitbucket Data Center
- Confluence Data Center
- Crowd Software Data Center
- Jira Software Data Center
- Jira Service Desk Data Center
Product | Repo | Marketplace |
---|---|---|
Bitbucket | ||
Confluence | ||
Crowd | ||
Jira Software | ||
Jira Service Desk |
The templates in this repository use Azure Cloud features to create a resilient and scaleable solution:
- Only Azure "managed" features/functionality used to provide scalability, monitoring, and backup/recovery features "out of the box."
- Security and accessibility principles/rules applied to ensure all customer data is protected.
- Optional SSL and CNAME/domain name support.
- Advanced monitoring and analytics the following integrated services:
- Azure Application Insights
- Azure Monitor
- Azure SQL Analytics
- Azure Gateway Analytics
- Log collection/aggregation.
- Database flexibility:
- You can deploy an Azure SQL DB or Postgres database.
- You can supply an existing Azure SQL DB or Postgres database.
- Integrated Azure Accelerated Networking for enhanced cluster performance.
- Recommended infrastructure/cluster sizing or fully configurable infrastructure options.
- Configurable Linux OS options for Jumpbox/VMs (Ubuntu LTS 16.04/18.04, RHEL 7.5, Centos 7.5, Debian Stretch 9-backports )
For more information on the Atlassian Azure solution, features, install options, and FAQs, check out Atlassian Azure Page
Each Atlassian application folder contains specific instructions on how to deploy the individual application, so always check there first. You can also find (and deploy from) the same templates on the Azure Marketplace:
- Jira Software Data Center
- Jira Service Desk Data Center
- Confluence Data Center
- Crowd Data Center
- Bitbucket Data Center
When you deploy using these Azure Marketplace templates, many parameters will be pre-configured for your convenience.
If you prefer a more customized deployment, you're welcome to use the templates in this repository directly. When you do, you'll need to deploy via the Azure CLI. Choose one of the following methods, depending on which tools you're comfortable with:
Both methods contain recommendations for overriding default deployment configurations through a custom parameters template. You can review the mainTemplate.json
file in each product directory to see what parameters you can override to customize your deployment.
Regardless of what you're installing, you'll always need to specify your jumpbox SSH key. Do this through the sshKey
parameter. This will allow you to connect via SSH to the jumpbox/bastion node (and then onto the cluster nodes). This key is your device's SSH public key (normally found at ~/.ssh/id_rsa.pub
). Cut/paste this value into the sshKey
parameter of your custom parameters template, like so:
{
"parameters": {
"sshKey": {
"value": "ssh-rsa AAAAo2D7KUiFoodDCJ4VhimXqG..."
}
}
}
Each set of product templates in this repository allows you to set more than just the jumpbox key. See Deployment customizations for more information.
Pull requests, issues and comments welcome. For pull requests:
- Add tests for new features and bug fixes
- Follow the existing style
- Separate unrelated changes into multiple pull requests
See the existing issues for things to start contributing.
For bigger changes, make sure you start a discussion first by creating an issue and explaining the intended change.
Atlassian requires contributors to sign a Contributor License Agreement, known as a CLA. This serves as a record stating that the contributor is entitled to contribute the code/documentation/translation to the project and is willing to have it used in distributions and derivative works (or is willing to transfer ownership).
Prior to accepting your contributions we ask that you please follow the appropriate link below to digitally sign the CLA. The Corporate CLA is for those who are contributing as a member of an organization and the individual CLA is for those contributing as an individual.