Deploying Jira Software Data Center in AWS

Great news! Jira Software Data Center deployments within AWS (Amazon Web Services) have just gotten easier. Why? Because an AWS Quick Start deployment package is now available. By automatically setting up multiple necessary items needed for Data Center to function correctly, this Quick Start package makes deploying Jira Data Center within AWS a snap.

Quick Start automatically sets up the following items in AWS:

  • Network infrastructure – To create the network infrastructure for your Jira deployment, a Virtual Private Cloud (VPC) is configured with both public and private subnets.
  • Internet access – Set up and configuration of an internet gateway.
  • Outbound internet access – Creation of managed network address translation (NAT) gateways in the public subnets to allow outbound internet access for resources that are in the private subnets. The Quick Start package deploys NAT instances in regions where NAT gateways are not available.
  • External database – In the private subnets, Quick Start deploys Amazon Relational Database Service (Amazon RDS) PostgreSQL as the external database for JIRA.
  • Auto scaling – An Auto Scaling group with JIRA instances based on Amazon Linux is created in the private subnets.
  • Shared file system for storage – Deployment of Amazon Elastic File System (Amazon EFS) as the shared file system for storage.
  • Choice of VPC – You can either create a new VPC or deploy into your existing VPC on AWS. The template that deploys the Quick Start into an existing VPC skips the network infrastructure, internet access and outbound internet access components described above.

Are the default settings right for you?

In order to get you up and running with little configuration, the Quick Start deployment package only sets up an “average scenario” data center for Jira. You need to consider a variety of items to determine whether or not the default settings for this average setup will be the best option for your deployment.

To do this you should first consider the projected size of your Jira instance. For example, how many users do you estimate will be using Jira? The more users that need to access Jira software data center, the more RAM you will require.

It’s also recommended that you pay attention to Amazon Elastic Block Store (EBS) volume options, especially the following factors:

  • 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 restricted to the baseline level.If there is any chance that this could happen, consider using a larger General Purpose SSD volume or switching to a Provisioned IOPS (SSD) volume. See for more information.
  • New EBS volumes have reduced performance the first time each block is accessed. See for more information.

Of course, the above EBS recommendations are based on a typical workload. The resource requirements of an actual Jira Software instance may vary markedly with several 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 that have 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.

Will the default settings be the right fit for your company? Before you implement the Quick Start deployment package, reach out to Coyote Creek for assistance in answering this important question. As Atlassian Platinum Partners we have the expertise to help you determine the settings that will be your best fit.