Currently Confluence stores the license details in the confluence.cfg.xml file, which is stored locally on each node.

When ever a license is installed on a node, the license details need to be distributed to each of the other nodes to be installed and stored in the confluence.cfg.xml file.

Prior to Confluence 5.6, license changes were not propagated across nodes (a bug). In Confluence 5.6, license changes are propagated to other nodes using the cluster event InternalLicenceUpdatedEvent.

The problem is that if a node is not active when a license is installed, it will not receive the cluster event InternalLicenceUpdatedEvent.

Workaround

• update the license key manually on the newly joined nodes which license key hasn't updated
• Alternatively, we strongly recommend you update the respective AMI every time a new license key is applied to the active node within the existing cluster.