Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Description
Problem Definition
Allow Confluence Standalone Server started with AWS Cloud Formation Template to upgrade by updating the Cloud Formation Stack
Upgradin the Confluence Standalone Server started using the ConfluenceServer.template.yaml needs to be manually carried out following the standard upgrade process instead of just updating the Cloud Formation Stack similar to the Confluence Data Center upgrade stated in the documentation below:
The main reason why is that Confluence Standalone Server doesn't persist the home directory when an EC2 node is brought down. Hence changing the Confluence Version in the stack and terminating the existing EC2 will lost the Confluence Home Directory
Suggestion
Allowing the Home Directory to be persisted even when the EC2 is terminated so the newly started EC2 after updating the stack can have a newer version while keeping the Home Directory data to proceed with the upgrade, similar to the Data Center.
This helps to cut down most of the manual work from upgrading the Confluence