Document limitations related to deploying JIRA using AWS CloudFormation Templates

Summary

Getting started with JIRA Data Center on AWS provides a method for deploying JIRA Data Center into AWS. The documentation can be used to deploy JIRA Data Center but there are some limitations and known issues that an admin should be aware of.

Examples:

• There are some known issues related to auto-scaling, such as offline node IDs not being removed from the cluster
  • JRASERVER-42916 and JRASERVER-65538
• Template does not allow for the selection of version to install/deploy
  • JRASERVER-65510
• Unsupported tags in setenv.sh file, in case Java version updated from 8 to Java 11 as documented in Unrecognized JVM GC options when using JAVA 11

Suggestion

Provide one location that describes known issues and limitations related to JIRA Data Center AWS Quickstart (CloudFormation) templates.

• Include details related to reporting new issues and limitations.
• Make it clearer that AWS Quickstart templates are recommended to be used only as a POC (proof of concept). We have the following details, however, this should be clearer to avoid unintended consequences with these CloudFormations.

"[The QuickStart CloudFormation Templates]should be treated as a reference implementation that shows how JIRA Data Center can be used with AWS, and be either used as-is, or serve as an example for creating your own template."