Getting started with Jira Data Center on AWS

Jira Data Center is an excellent fit for the Amazon Web Services (AWS) environment. Not only does AWS allow you to scale your deployment elastically by resizing and quickly launching additional nodes, it also provides a number of managed services that work out of the box with Jira Data Center instances and handle all their configuration and maintenance automatically.

Interested in learning more about what Jira Data Center provides? Click here for an overview.

On this page:

Deploying Jira Data Center using the AWS Quick Start

The simplest way to deploy your entire Data Center cluster in AWS is by using the Quick Start. The Quick Start launches, configures, and runs the AWS compute, network, storage, and other services required to deploy a specific workload on AWS, using AWS best practices for security and availability.

The Quick Start provides two deployment options, each with its own template. The first option deploys the Atlassian Standard Infrastructure (ASI) and then provisions either Jira Software or Jira Service Desk Data Center into this ASI. The second option only provisions Jira Software or Jira Service Desk Data Center on an existing ASI.

Atlassian Standard Infrastructure (ASI)

The ASI is a virtual private cloud (VPC) that contains the components required by all Atlassian Data Center applications. For more information, see Atlassian Standard Infrastructure (ASI) on AWS.


Here's an overview of the architecture for the Jira Data Center Quick Start:

The deployment consists of the following components:

  • Instances/nodes. One or more Amazon Elastic Cloud (EC2) instances as cluster nodes, running Jira.
  • Load balancer. An Amazon Elastic Load Balancer (ELB), which works both as load balancer and SSL-terminating reverse proxy.
  • Amazon EFS host: A shared file system for storing artifacts in a common location, accessible to multiple Jira nodes. The Quick Start architecture implements the shared file system using the highly available Amazon Elastic File System (Amazon EFS) service.
  • Database. An Amazon Relational Database (RDS) instance as the shared database.
  • An Amazon Elasticsearch Service domain for code and repository search.

For more information, see Jira products on AWS.

Use the Quick Start as is or develop your own

To get you up and running as quickly as possible, the Quick Start doesn't allow the same level of customization as a manual installation. You can use our templates either as is, or as a reference for creating your own template. 

Amazon Aurora database for high availability

The Quick Start also allows you to deploy Jira Data Center with an Amazon Aurora clustered database (instead of RDS). 

This cluster will be PostgreSQL-compatible, featuring a primary database writer that replicates to two database readers. You can also set up the writers and readers in separate availability zones for better resiliency.

If the writer fails, Aurora automatically promotes one of the readers to take its place. For more information, see Amazon Aurora Features: PostgreSQL-Compatible Edition.

For instructions on manually setting up a new Amazon Aurora clustered database and connecting it to Jira Data Center, see Connecting Jira Data Center to Amazon Aurora. Amazon Aurora is supported on Jira Software 8.4, Jira Service Desk 4.4, and all later versions of both.

Auto Scaling groups

This Quick Start uses Auto Scaling groups, but only to statically control the number of its cluster nodes. We don't recommend that you use Auto Scaling to dynamically scale the size of your cluster. Adding an application node to the cluster usually takes more than 20 minutes, which isn't fast enough to address sudden load spikes.

If you can identify any periods of high and low load, you can schedule the application node cluster to scale accordingly. See Scheduled Scaling for Amazon EC2 Auto Scaling for more information. 

To study trends in your organization's load, you'll need to monitor the performance of your deployment. Refer to Jira Data Center sample deployment and monitoring strategy for tips on how to do so. 

Supported AWS regions

Not all regions offer the services required to run Jira.  You'll need to choose a region that supports Amazon Elastic File System (EFS). These regions are:

  • Americas
    • Northern Virginia
    • Ohio
    • Oregon
    • Northern California
    • Montreal
  • Europe/Middle East/Africa
    • Ireland
    • Frankfurt
    • London
    • Paris
  • Asia Pacific
    • Singapore
    • Tokyo
    • Sydney
    • Seoul
    • Mumbai

This list was last updated on .

The services offered in each region change from time to time. If your preferred region isn't on this list, check the Regional Product Services table in the AWS documentation to see if it already supports EFS. 

The Paris region in Europe/Middle East/Africa also supports EFS. However, our Quick Start uses the db.m4 instance class, which isn't available yet in this region. We will be updating our templates soon to support the db.m5 instance class, which will then allow you to use our Quick Start in the Paris region.

Related pages:

Last modified on Aug 8, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.