Tutorials and documents for deploying JIRA on AWS are talking about DataCenter version of JIRA (https://s3.amazonaws.com/quickstart-reference/atlassian/jira/latest/doc/jira-software-data-center-on-the-aws-cloud.pdf).
We want to deploy DataCenter at some point on AWS, but for the time being we first want to make POC and test it with JIRA Server before migrating to DataCenter.
My question is - is possible to deploy / host JIRA Server on AWS, are installation and procedures described in the above document applicable to JIRA Server, if yes are there any differences in the sense of installation, deployment and behaviour and can we later easily migrate to DataCenter?
Rather late to this party but when running Jira on AWS with EFS volumes I ran into a latency issue.... which caused me to migrate to EBS. Perhaps with the active-active of datacenter the latency problem goes away...
EFS was my preferred choice but ended up being bad juju.
Hi @Mike Rathwell-
Can you share any metrics on the size of your instance?
Generics like users or projects would be helpful, but ideally throughput on the EBS volume.
EFS is easy to get up and running but I'm curious if we'll be able to provision sufficient IOPS.
Thanks in advance!
SO... i have a 500 user instance but it is pounded heavily and has a lot of massively expensive groovy listeners and automation stuff in it. I have a 500GB volume for Jira (don't get me started on why that has to be so large but a change is coming) and a 25GB volume for Confluence with no extra throughput provisioned. I've never seen the burst balance drop below 98% on either of those volumes. The rough days are the sprint planning days where a lot of users are viewing the same issues (each having far too many groovy calculated fields) and automations to force things to happen on even mundane issue changes ALONG WITH enterprise agile poker. Some boards in use during these festivals span literally dozens of projects.
As noted before, I was NEVER hitting I/O or IOPS limits and don't even on the heavy days. I seldom see volume I/O above 2Mb/s or IOPS above 200. Always turned out to be latency. AWS came back with some suggestions that feel like "here, try this" so I went EBS.
I think if you're going Data Center (which requires EFS on AWS to work) you'd be fine as it is far more likely that you'll have a non-busy resource available for a given operation.
One thing I did recently as I was running out of CPU (which caused a whole raft of other issues with eating DB connections, swamping disk, etc) was increase my instance size AND changed from an m4 to a c5 instance type. This seems to have more disk I/O available to it as well since I DO now see burst balance consumed once in a while and not like the seldom times it dropped below 100% as it was before.
Thanks much for the details Mike!
I hadn't understood the issue might be on latency rather than IOPS. Hadn't realized this from my first read, so this is a particularly valuable insight.
We're also on a 500 user instance, but with a smaller data set and less intense automation from the sounds of it, so I'm at least hopeful that EFS will cover our usage.
Hey @Jeff Everett,
Yes, it DOES sound like you could go EFS. As I mentioned originally, that was my first choice for a variety of reasons:
When I go Data Center (will be sometime in the next year as I just paid this year's maintenance and it's a non-trivial exercise besides) I am looking forward to regaining these EFS benefits.
Yes, you can install JIRA Server on AWS. And later migrate to Datacenter.
The instructions will be similar but you don't need a load balancer and multiple nodes.Check out https://confluence.atlassian.com/adminjiraserver071/installing-jira-applications-802592161.html
It's not an officially supported platform in https://confluence.atlassian.com/display/AdminJIRAServer072/Supported+platforms but plenty of people are using it, and if Data Center works there, JIRA Server products should work as well
I don't run the billing so only have a high level view of that but, after buying Reserved Instances for my prod and test envs, and careful sizing I am keeping it ~$1500/mo for the whole thing (all elements used considered and not just the basic EC2, EBS, RDS kinda stuff)
The roof is on FIRE… network outages, broken processes, upset clients and employees. Each day seemed to bring more and more issues. Incidents were communicated via email, messengers (skype or teams) ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events