Jira Software Data Center on AWS (Part Two)
In my previous blog, I discussed the benefits of AWS and the benefits of setting up Jira Data Center on AWS. I also created our Stack on AWS CloudFormation. In this installment, I will continue this discussion and finish by talking about the Jira installation.
Step 5: Configuring Jira
To retrieve the URL required to access your Jira instance, you can either open the Stack details page and look under the Outputs header for the URL key, or go to the EC2 Management Console and use the value “DNS name” for the Load Balancer.
Setting up the Jira instance is as simple as going through the remaining wizard and entering the license information. Users will probably need a Jira Data Center evaluation license in order to do this. You can contact firstname.lastname@example.org to get an evaluation license.
The next step is to create the local admin account, set up the SMTP details, and follow the remaining steps in the wizard.
Users can now choose to continue setting up their Jira instance.
Step 6: Adding nodes to the cluster
If a Jira Data Center license has been installed into Jira, administrators will be able to see the cluster details under “Administration > System Info.”
Note that the cluster name will correspond to the EC2 Instance ID.
As mentioned in my previous blog, one benefit of using the Quick Start template is the ability to quickly scale the number of nodes up or down. In this case, we will be adding one more node to the Jira instance.
To do this, we need to:
- Sign into the AWS Management Console > AWS CloudFormation at https://us-west-2.console.aws.amazon.com/cloudformation.
- Select the correct Stack and click “Update Stack.”
- Click “Next” to reach the Specify Details page and increase the minimum and maximum number of cluster nodes to the desired value.
- Save the form and wait for the new node to come up. Administrators should now be able to see two nodes in the cluster.
Jira 7.3 for Data Center introduces a number of functionalities that provide added benefits for this setup. This includes the highly requested SAML single sign-on with the user’s current supported Identity Provider. This is Atlassian’s attempt to provide users with a single sign-on experience. Also, Jira 7.3 brings “zero downtime upgrades” that allow nodes to provide uninterrupted service to Jira users. These two functionalities go hand in hand with hosting the application in AWS.
For more information about Jira on AWS, or to learn how Go2Group can assist with hosting services, contact us.