Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo shared credentials, missing SSH option


Following your article here, I should be able to save the private key, however I only have the option of AWS.


Does anyone have any idea of what I need to do to enable the SSH option?


We are using Bamboo Server (On premise) version  6.6.1 build 60605 - 04 Jul 18



1 answer

1 vote
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 23, 2018

Hello Adrian,

  • Have you added the SSH key at Cog >> Overview >> Shared credentials?
  • Can you share where you are trying to use the SSH key, in what task?

Hi @Daniel Santos,

Thanks for your reply,

This is my issue, under Cog >> Overview >> Shared credentials, there is no `SSH` option:


I'm trying to add the shared SSH key, so that I can use it in tasks.


Many thanks 

Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 27, 2018

It looks like the plugin Shared Credentials is disabled in your instance.

I was able to reproduce the same scenario by disabling its two modules:

  • SSH (sshCredentials)
  • Username and password (usernamePasswordCredentials)

Moving forward

  1. Try to enable the modules again:
    1. Admin page >> Manage add-ons
    2. Select All add-ons in the drop down
    3. Search for Shared Credentials
    4. Click add-on and then X of 2 modules enabled
    5. Click enable on each module disabled if there are any
  2. If you cannot enable the modules using the method above or if they show up as enabled, please try to restart the instance and check if this issue was fixed. It is possible that this issue was caused by a startup issue when loading the system add-ons.

In case this didn't help we will probably need to open a support case to investigate this further.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events