Upgrading Jira Data Center on AWS should instruct customers to shut down JIRA gracefully before terminating from AWS

Issue Summary

https://confluence.atlassian.com/adminjiraserver/upgrading-jira-data-center-on-aws-945105105.html is missing potentially critical step that could lead to higher customer friction, i.e. L1s and L2s created for support

Expected Results

in Option 1 Step 1 we should state that customers should Stop JIRA gracefully on all the nodes before terminating them from AWS console

While in AWS when node is terminated, EC2 instance is supposed to recieve a signal to terminate instance and systemd service manager should stop the services and allow them to wrap up their processes, this might not always work and the node will get terminated abruptly, which could be similar to flicking the power off switch, whiconh could actually result in data corruption

If customer is having an issue logging in to the node before terminating, they should contact AWS Support and use terminate option only when absolutely certain that JIRA is stopped on all the nodes before proceeding with the upgrade

Steps to Reproduce

Open the linked article

Actual Results

We simply state that customers could terminate all nodes right away

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available