Running Jira on an Azure cluster
The Azure ARM template as a method of deployment is nearing its end-of-support date on May 31, 2023. You can still use the template after this date but we won't maintain or update it.
We recommend deploying your Data Center products on a Kubernetes cluster using our Helm charts for a more efficient and robust infrastructure and operational setup. Learn more about deploying on Kubernetes
If you decide to deploy Jira Data Center in a clustered environment, consider using Microsoft Azure. This platform allows you to scale your deployment elastically by resizing and quickly launching additional nodes and provides a number of managed services that work out of the box with Jira Data Center. These services make it easier to configure, manage, and maintain your deployment's clustered infrastructure.
We've set up reference templates that let you deploy Jira Software Data Center and Jira Service Desk Data Center in Microsoft Azure, and you can then configure it depending on your organization's needs. We strongly recommend you to set up user management, central logging storage, a backup strategy, and monitoring, just as you would for a Jira Data Center installation running on your own hardware.
On this page:
Non-clustered VS clustered environment
A single node is adequate for most small or medium size deployments, unless you need high availability or zero-downtime upgrades.
How it works
Here's an architectural overview of what you'll get when deploying Jira Data Center using the templates:
The deployment contains one or more Azure standard VM instances as application cluster nodes in a scale set. Each node runs Jira Software or Jira Service Desk, depending on which template you use.
The template also provisions an Azure Files storage account for the shared home. This shared home stores attachments and other files accessible to the application cluster nodes. It's mounted as a SAN drive on each cluster node and treated normally like any other file.
Standardized infrastructure
| Component | Configuration |
|---|---|
| Bastion host | This is a lightweight but highly secure Azure Linux VM that controls SSH access to the application cluster nodes. |
| Application Gateway | By default, this gateway is composed of two instances for high availability. It acts as a HTTP/HTTPS load balancer for your scale set of application cluster nodes. |
| Monitoring | The ARM templates configure Azure Monitoring to perform basic health and availability monitoring to cluster nodes and database. |
| Database | You can choose between Azure SQL Database (MS SQL Server-compatible) or Azure PostgreSQL database. Either way, the database will be configured as service endpoints to only allow traffic from the private network that the cluster nodes are in. This restricted traffic setup helps enhance security. |
Migrating to an Azure deployment
You can also migrate your existing Jira Data Center instance into Azure. To do this, you will need to set up a new Jira Data Center instance in Azure, and then import data from your existing instance. This approach ensures that your new site is created with optimum settings for Azure.
Here’s a high-level overview of the steps.
Before you begin
Back up your existing Jira instance, including your database and home directories.
Steps
- Make a list of any Marketplace or other user-installed apps.
- Export the data into XML format. The attachments won't be exported, so you need to manually copy them from your current shared home directory.
- Deploy Jira Data Center in Azure, and test that Jira is working as expected.
- Import the XML backup that you created before.
- Copy the contents of your /attachments directory to the equivalent directory in your shared home directory in Azure.
- Install any apps that you used before.
- Test your new Jira Data Center instance.
Securing your Azure deployment
We recommend deploying Jira with SSL. Our template will prompt you for a certificate and password.
Good to know:
- HTTPS is terminated at the application gateway.
- Your certificate should be from a trusted Certificate Authority. You should avoid self-signed certificates.
Preparing for your deployment
1. Determining the size of your deployment
While deploying Jira Data Center on Microsoft Azure, you’ll have an option to choose the size of your deployment—small, medium, large, or enterprise. This will determine the number of Jira application nodes, and the size of VMs to be provisioned.
To help you estimate your instance’s size, we identified several Jira Data Center size profiles that are based on the amount of data dimensions that you already have, or are planning to have, such as the number of issues, projects, custom fields, users, and so on. For more information, see Jira Data Center size profiles.
2. Choosing the region
The region, or location, is where Azure will house your deployment. Some regions don’t provide all Azure features, like access to Application Insights and analytics. The choice here depends on what features would you like to use for your deployment.
To browse regions and available features, see Products available by region.
3. Preparing additional information
During the deployment, you will also need:
- (Optional) SSL: A Base64 encoded PFX certificate from a trusted Certificate Authority.
- (Optional) CNAME: Details of your existing CNAME, if you don't want Azure to generate a random domain for you.
Deploying Jira Data Center to Azure via Azure Marketplace
This method uses the Azure Marketplace to deploy Jira Software Data Center or Jira Service Desk Data Center using our deployment templates as a reference.
To deploy Jira Data Center to Azure using our Marketplace app:
- Sign in to Azure Portal.
- Select Create a resource to start a new deployment
- Search for Atlassian, then select Jira Software Data Center or Jira Service Desk Data Center from the list of Marketplace apps.
- Select Create to start configuring the deployment.
- Follow the prompts in the wizard to configure your deployment. Refer to the following parameters table for more information.
- Confirm all the details are correct, then select Create to purchase the subscription. Deployment will take about 30 minutes.
- Once deployment is complete, go to the Jira URL listed in the deployment outputs to complete onboarding and start using Jira.
Jira-specific parameters
The following parameters apply only to Jira Software and Jira Service Desk.
| Jira version | Specify the version of Jira you'd like to install in full. For example, 7.13.0. We'd recommend that you choose Jira Software 7.13 or later or Jira Service Desk 3.16 or later. These versions have been thoroughly tested in Azure. Head to Jira Software Release Notes or Jira Service Desk Release Notes for a list of all releases. |
|---|---|
| Jira admin credentials | Provide a name and password for the initial Jira administrator on your instance. |
| Jira cluster | Select the expected size of your site—trial, small, medium, large, or enterprise. This will determine the number of Jira application nodes and the size of VMs to be provisioned. Select Change Size to override the defaults. |
Standardized infrastructure parameters
| Parameter | Description |
|---|---|
| Subscription | Your Microsoft Azure subscription type. |
| Resource group | If you have an existing resource group, you can use it, or create a new one. |
| Location | This is the region where Azure will house your deployment. |
| SSH Access | Provide an SSH public key to be used to SSH into the instance that will act as bastion host, and a username and password for SSH access to the Bitbucket nodes. See Create and use an SSH public-private key pair for Linux VMs in Azure in the Microsoft Azure documentation. |
| Database configuration | Choose between an Azure SQL Database, or Azure Database for PostgreSQL. Provide a username and password for the database admin user. Existing databases If you want to integrate with an existing database, you'll have to deploy to Azure using the CLI. |
| CNAME | This is the Canonical Name record (CNAME) for your organization. If you don't provide one, Azure will generate a random sub domain for your instance. |
| HTTP/SSL | Provide the certificate and password to be used for SSL termination on the Azure Application Gateway. |
| Monitoring | Choose the monitoring and analytics services that you would like to enable. Subject to availability in your location. See Monitoring for related information. |
Deploying Jira Data Center to Azure using the CLI
This method uses the Azure command-line interface to deploy Jira Data Center using our deployment templates as a reference. You'll need to install the Azure CLI to do this.
Using the deployment templates directly allows for greater configuration granularity. All hardware choices such as the number of cluster nodes, size, disk size, and OS type are configurable as parameters.
Head to atlassian-azure-deployment in Bitbucket and check out the README to find out how to deploy using the CLI.
Monitoring
As a number of the resources we provision are managed by Azure, a number of options are available for monitoring. For example:
The application gateway will automatically monitor its backend pool (the Jira application nodes), sending the alerts to the Jira admin email address specified in the deployment. See Application Gateway health monitoring overview in the Microsoft Azure documentation.
Application Insights can be used to see the overall system health and dig into particular areas of interest Application Insights in the Azure documentation.
- Azure SQL Analytics is available for more granular monitoring of your SQL Server database. Monitor Azure SQL Database using Azure SQL Analytics in the Microsoft Azure documentation.
Note that some of these resources are still in preview, so may not be available in your region yet.