Migrating a Quick Start deployment to a different S3 bucket
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Purpose
Normally, when you deploy Confluence Data Center using our AWS Quick Start, we recommend that you:
Create your own S3 bucket.
Clone the Quick Start templates and edit them to use this bucket.
Upload your clone of the Quick Start templates your S3 bucket.
Update your deployment to use that bucket’s templates.
If you deployed directly from the original AWS Quick Start, changes to the Quick Start templates will automatically propagate to your deployment. These updates sometimes involve adding or removing parameters from the templates. This could introduce unexpected (and possibly breaking) changes to your deployment.
Solution
Your deployment needs to be based on templates stored on your own S3 bucket. This will quarantine your deployment from unexpected changes to the AWS Quick Starts.
Option 1: Re-deploy from templates in your own S3 bucket (for nested database stacks)
We introduced nested stacks to the AWS Quick Start for Confluence on . If you used the AWS Quick Start after this date, then your deployment uses nested database stacks.
If this is the case, then you’ll have to re-deploy from scratch. When you do, you’ll need to use templates from your own S3 bucket. See Deploying the Quick Start from your own S3 bucket (recommended) for instructions .
Option 2: Re-base your existing deployment on separate templates (for non-nested database stacks)
Create your own S3 bucket.
Download the templates used by your deployment.
Recreate the original AWS Quick Start’s directory structure on your S3 bucket.
Update your deployment to use the templates from your bucket.