Issue Summary

The guide for installation of Bitbucket Data Center in AWS is fewer than Confluence Data Center in AWS, especially reagarding Node Discovery.

Please provide the setting guide for Node Discovery in AWS.

This is reproducible on Data Center: yes

Suggestion

Please provide the setting guide for Node Discovery in AWS like the following Confluence one.

(Confluence)Change Node Discovery from Multicast to TCP/IP or AWS

Actual Results

There is no detailed Bitbucket DC guide for installation in AWS.
The related documents are only existing in the following.

• Install Bitbucket Data Center
  • > Using multicast to discover cluster nodes (hazelcast.network.multicast=true) is recommended, but requires all your cluster nodes to be accessible to each other via a multicast-enabled network. If your network does not support multicast then you can set hazelcast.network.multicast=false, hazelcast.network.tcpip=true, and hazelcast.network.tcpip.members to a comma-separated list of cluster nodes instead. Only enable one of hazelcast.network.tcpip or hazelcast.network.multicast, not both.
• Configuration properties
  • > hazelcast.network.aws
  • > A boolean flag to indicate whether Hazelcast has AWS EC2 Auto Discovery enabled. When setting this property to true, either hazelcast.network.aws.iam.role or (hazelcast.network.aws.access.key and hazelcast.network.aws.secret.key) become required properties.

Workaround

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