Use the jira-config.properties file to customize an AWS Quick Start deployment
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This article covers how to use the jira-config.properties file to customize a Jira Data Center instance deployed via the AWS Quick Start.
This article assumes that you already have a jira-config.properties file. For more information on that, see How to Edit the jira-config.properties File in Jira Data Center and Advanced Jira application configuration.
Solution
All of our AWS Quick Starts use Ansible playbooks to configure specific components of your deployment. These playbooks run automated tasks that set up each application node of the AWS Quick Start deployment. One of these tasks is to check if the shared home contains a jira-config.properties file. If there is, then the file will be applied to all new application nodes. This allows you to use the jira-config.properties file to apply advanced customizations to your application nodes.
Step 1: Copy jira-config.properties to the shared home
First, upload the jira-config.properties file to your shared home. To do this, copy jira-config.properties to /media/atl/jira/shared/ on any application node. For instructions on how to do this, see Connecting to your nodes over SSH.
Step 2: Find all the current application nodes in your stack
In AWS, note the Instance IDs of all running application nodes in your stack. To do this:
In the AWS console, go to Services > CloudFormation. Select your deployment’s stack to view its Stack Details.
Expand the Resources drop-down. Look for the ClusterNodeGroup and click its Physical ID. This will take you to a page showing the Auto Scaling Group details of your Jira application nodes.
In the Auto Scaling Group details, click on the Instances tab. Note all of the Instance IDs listed there; you'll be terminating them in Step 3.
Step 3: Terminate all nodes
In the previous step, you noted all of the Instance IDs of all application nodes. You'll need to terminate them now.
In the AWS console, go to Services > EC2. From there, click Running Instances.
Check all of the instances matching the Instance IDs you noted in Step 2.
From the Actions drop-down, select Instance State > Terminate.
Click through to terminate the instances.
Once you terminate all nodes, AWS will automatically replace them. Each time a replacement node is provisioned, the jira-config.properties file will be copied from the shared home to the node's local home. This will apply the settings from jira-config.properties file to the node.
Was this helpful?