Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Update Confluence license programmatically

Hi all, 

I am looking at implementing auto scaling with our Confluence cluster however it looks like the license needs to be replaced every time a new node is spun up. 

Is it possible to set the license programmatically? via api or another method?


4 answers

0 votes
Fadoua Community Leader May 30, 2021

@Adam Wickes 

Not sure I ever heard about this feature(meaning rest api to update the license).

I know it is annoying however it has to be done everytime you install confluence on a new server.



Even when they're part of a cluster?

I thought it might be possible to copy license value from one node to another but it looks like both nodes have exactly the same value in confluence.cfg.xml. Is the only way to add a new license via the gui?

0 votes
Fadoua Community Leader May 31, 2021

@Adam Wickes  If it is the same license you will be using in your different environments then you can have license copied via automation. When I say automation I mean you have  to do all your installs/upgrades using BitBucket and Jenkins (or other tools of your choice)

But if you are doing everything manually you will have to update the license yourself.



Hi Fadoua, 

it's the same cluster. 
We are using auto scaling to cycle the nodes daily.
Each day, the new node requires us to manually enter the license number again.
I have checked confluence.cfg.xml on both nodes and it looks like the license.message property is identical on both so unsure why one node is ok and one asks for license to be entered again.


Just an update on this. I was incorrect regarding the licence values. Both nodes had similar values but not the same. Copying the value from one to the other and then restarting the confluence service does work.

This is a long shot but is there any way I can get the encrypted value from the actual license key without having to push it through the gui? It would be super handy to be able to store the encrypted license value in AWS systems manager/secrets manager and then pull it into the node during the user data execution.

0 votes
Fadoua Community Leader May 31, 2021

not sure @Adam Wickes let me tag an expert here @Daniel Eads can you please assist Adam?

0 votes
Daniel Eads Atlassian Team Jun 02, 2021

Hey @Adam Wickes ,

I wanted to direct you to the Installing Confluence Data Center document, which has this information about adding additional nodes:

Copy Confluence to second node

To copy Confluence to the second node:

  1. Shut down Confluence on node 1.
  2. Copy the installation directory from node 1 to node 2.
  3. Copy the local home directory from node 1 to node 2.

Copying the local home directory ensures the Confluence search index, the database and cluster configuration, and any other settings are copied to node 2.

So that's the standard non-autoscaling way of doing things. When copying the install directory over, confluence.cfg.xml will be included and you shouldn't need to modify the license.


For AWS-specific deployments, our Confluence Data Center AWS Quickstart template should handle tasks like that when autoscaling. I'm guessing you haven't already deployed with the Quickstart (hence the licensing problem you've noted). I would suggest redeploying with the Quickstart if possible, as it takes care of a number of pieces that should make your autoscaling simpler.


We have deployed using that quickstart guide.
Every time a new node starts, it is created with the default key and not the key manually applied to the first node.

Daniel Eads Atlassian Team Jun 03, 2021

Hi @Adam Wickes ,

In that case, I might suggest opening a case through our support portal so that we can take a look at your AWS configuration. Reviewing your account, you'll either need to reach out to a technical or billing contact for your Confluence Data Center's license, or get added as a contact on the license in order to open a case at . The folks who are able to open a case with support will see the Confluence Data Center license when they check .


Can I just confirm Daniel that using the quickstart guide still means entering the license manually? 

Step 3 of the quick start guide is:

"On the License key page, enter a valid Confluence Data Center license, and then choose Next."

So my question is this.... when a node is auto scaled, wouldn't we still need to manually perform that step?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Miss the Confluence demos at Team 21? Watch them here!

Phew, Atlassian Team 2021 blew by. With dozens of demos and a handful of keynotes, you may have missed some of the awesome Confluence Cloud sessions. Don't' worry, you can watch them all here or on Y...

394 views 2 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you