Details
-
Bug
-
Resolution: Fixed
-
High
-
6.2.0, 6.3.1
-
1
-
Severity 2 - Major
-
Description
When attempting to deploy Confluence to some AWS regions Synchrony will not start properly because of AWS API using the wrong endpoint. The effected regions are:
- US East (Ohio) - us-east-2
- EU (London) - eu-west-2 - See Note 1
- Asia Pacific (Mumbai) - ap-south-1 - See Note 1
- Asia Pacific (Seoul) - ap-northeast-2 - See Note 1
- Canada (Central) - ca-central-1 - See Note 1
Note 1: presently does not support EFS which is required to deploy on AWS using the Atlassian CloudFormation template
Workaround
a. Use a different region to deploy Confluence
or
b. Do not deploy Synchrony and disable Collaborative Editing in Confluence
Attachments
Issue Links
- Testing discovered
-
CONFSERVER-52985 For some instance type (ex I2.xlarge), Confluence could not download and install properly because the failure when mounting to ephemeral0
- Closed
- mentioned in
-
Page Loading...