I'm trying to setup Bamboo with EC2. I've got some jobs that are failing, so I'd like to login to the instance to view where it got caught up and troubleshoot the issue.
The issue is, the .pk key provided on bamboo for the instance has never worked. I've looked thru other questions and see responses like "someone else in your orginization changed it" but it's just me... I'm using the stock AMI, I have not changed a thing.
I've tried terminating the instance and re-loading it many times, no matter what I try, I can't get access.
If I spin up my own copy of the same AMI from the AWS management console and assign a differnt key to it, it works, but I can't get into the instances Bamboo spins up.
$ ssh -i elasticbamboo.pk firstname.lastname@example.org
Permission denied (publickey).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs