Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-58540

Allow Confluence Standalone Server started with AWS Cloud Formation Template to upgrade by updating the Cloud Formation Stack

    XMLWordPrintable

Details

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    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

      Attachments

        Activity

          People

            Unassigned Unassigned
            btan@atlassian.com Damien Tan
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: