What does one have to do these days to get a Jira DC running on AWS (especially the flavor with an existing dataset of 1M issues)? I tried the "AWS Quick Start for Jira Data Center" several times, but every time it fails with a (different) error message and rolls back.
The last error was something like: could not create "BastionHost", but it never really says why its creation attempts fail.
Of course, it would be much much much easier to just install locally, but for the DC Apps Approval process we're supposed to run comparable instances and it explicitly mentions AWS. AFAIK the "dc-app-performance-toolkit" also seems to require AWS.
Solution seems to be: Try several times until it works.
Performance and reliability also seems extremely dependent on time of day.
Yesterday in the morning (US eastern time) a reindex took two hours and failed with an error.
Right now (night in US eastern time), the reindex took 37 minutes.
My hunch is that you should probably avoid AWS when other people use it (or get something different from a c5.4xlarge instance; I'm not familiar with details or performance guarantees).
Hi @Ulrich Hobelmann [catworkx]
Can you confirm that you have selected the correct region?
Not all regions offer the services required to run Jira. You'll need to choose a region that supports Amazon Elastic File System (EFS). These regions are:
For more information :
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, I selected North Virginia explicitly because of the EFS requirements.
But thanks for the links, I'll check them out, in case I missed something else.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This time it could not start the JiraDCStack, because "AWS was not able to validate the provided access credentials (Service: AmazonAutoScaling;...)" (and this aborts the ClusterNodeGroup, which aborts the rest of everything).
Is that something I have to enable globally somewhere (what Google gave me didn't look like it, but I'm not an AWS expert)? To start the template, I explicitly had to tick the checkbox to allow Autoscaling, so I thought that was it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting, now it seems like it worked. So it's just a bit non-deterministic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.