Recommendations for running JIRA Software Data Center in AWS
This page provides general sizing and configuration recommendations for running self-managed JIRA Software Data Center instances on Amazon Web Services (AWS).To get the best performance out of your JIRA Software Data Center deployment in AWS, it's important to not under-provision your instance's CPU, memory, or I/O resources. Note that the very smallest instance types provided by AWS do not meet JIRA's minimum hardware requirements and aren't recommended in production environments. If you don't provision sufficient resources for your workload, JIRA is likely to exhibit slow response times, or possibly fail to start altogether.
Recommended EC2 and EBS instance sizes
On this page
JIRA Software Data Center (cluster nodes)
|Active Users||EC2 instance type||Recommended number of nodes|
0 – 250
|250 – 500||c3.xlarge||1-2*|
|500 – 1000||c3.2xlarge||2|
|1000 – massive scale||c3.4xlarge+||3+|
* For high-availability, we recommend deploying 2 or more cluster nodes as a minimum.
JIRA Software Data Center (shared file server)
These recommendations assume a single EC2 instance with attached EBS volume acting as a shared EFS server for the cluster.
|Active Users||EC2 instance type||EBS Volume type||IOPS|
0 – 250
|m4.large||General Purpose (SSD)||N/A|
|250 – 500||m4.xlarge||General Purpose (SSD)||N/A|
|500 – 1000||m4.2xlarge||Provisioned IOPS||500 – 1000|
|1000 – massive scale||m4.4xlarge+||Provisioned IOPS||1000+|
The Amazon Elastic File System (EFS) is supported for JIRA's shared home directory at this time.
In JIRA Software instances with high hosting workload, RAM is often the limiting factor. The more users that need to access JIRA Software, the more RAM you will require. It's also recommended that you pay particular attention to EBS volume options, especially the following:
- The size of an EBS volume also influences I/O performance. Larger EBS volumes generally have a larger slice of the available bandwidth and I/O operations per second (IOPS). A minimum of 100 GiB is recommended in production environments.
- The IOPS that can be sustained by General Purpose (SSD) volumes is limited by Amazon's I/O credits. If you exhaust your I/O credit balance, your IOPS will be limited to the baseline level. You should consider using a larger General Purpose (SSD) volume or switching to a Provisioned IOPS (SSD) volume. See Amazon EBS Volume Types for more information.
- New EBS volumes in particular have reduced performance the first time each block is accessed. See Pre-Warming Amazon EBS Volumes for more information.
The above recommendations are based on a typical workload with the specified number of active users. The resource requirements of an actual JIRA Software instance may vary markedly with a number of factors, including:
- Whether the majority of traffic to JIRA Software is over HTTP or SSH, and the encryption ciphers used
- The number and size of issues: JIRA Software will use more resources when you work on many issues with large attachments
- The activity of your users: JIRA Software will use more resources if your users are actively using the JIRA Software web interface to browse, search, and work on issues
Other supported instance sizes
The following Amazon EC2 instances also meet or exceed JIRA Software's minimum hardware requirements. These instances provide different balances of CPU, memory, and I/O performance, and can cater for workloads that are more CPU-, memory-, or I/O-intensive than the typical.
|Model||vCPU||Mem (GiB)||Instance Store (GB)||
|c3.xlarge||4||7.5||2 x 40 SSD||Yes||-|
|c3.2xlarge||8||15||2 x 80 SSD||Yes||-|
|c3.4xlarge||16||30||2 x 160 SSD||Yes||-|
|c3.8xlarge||32||60||2 x 320 SSD||-||-|
|i2.xlarge||4||30.5||1 x 800 SSD||Yes||-|
|i2.2xlarge||8||61||2 x 800 SSD||Yes||-|
|i2.4xlarge||16||122||4 x 800 SSD||Yes||-|
|i2.8xlarge||32||244||8 x 800 SSD||-||-|
|m3.large||2||7.5||1 x 32 SSD||-||-|
|m3.xlarge||4||15||2 x 40 SSD||Yes||-|
|m3.2xlarge||8||30||2 x 80 SSD||Yes||-|
|r3.large||2||15.25||1 x 32 SSD||-||-|
|r3.xlarge||4||30.5||1 x 80 SSD||Yes||-|
|r3.2xlarge||8||61||1 x 160 SSD||Yes||-|
|r3.4xlarge||16||122||1 x 320 SSD||Yes||-|
|r3.8xlarge||32||244||2 x 320 SSD||-||-|
|x1.32xlarge||128||1,952||2 x 1,920 SSD||Yes||10,000|
In all AWS instance types, JIRA Software only supports "large" and higher instances. "Micro", "small", and "medium" sized instances do not meet JIRA Software's minimum hardware requirements, and aren't recommended in production environments.
In any instance type with available Instance Store device(s), a JIRA Software instance launched from the JIRA Software AMI will configure one Instance Store to contain JIRA Software's temporary files and caches. Instance Store can be faster than an EBS volume but the data doesn't persist if the instance is stopped or rebooted. Use of Instance Store can improve performance and reduce the load on EBS volumes. See Amazon EC2 Instance Store for more information.
Was this helpful?
Thanks for your feedback!