I'm using a Bamboo Amazon EC2 Windows 2008 Server VM for my CI server and I see there is a "Bamboo" user created on the VM and that when Bamboo starts a build, it runs under this user. I would like to be able to RDP to the VM as the Bamboo user so I can perform some set up operations.
I am aware that I can find the Administrator password on the Bamboo website and login as the Administrator, but I want to actually login as the Bamboo user that the builds run under, how can I do that?
Remote login for user Bamboo is disabled for security reasons (we cannot randomise passwords for that user). You can reenable it (but remember to change the password first).
To make that change permanent, you need to create a new image.
Ok can do, once I change the password on the Bamboo user and create a new AMI, do I need to update the password on the Bamboo website somewhere, in addition to the AMI ID?
I see I can update the AMI ID on the Edit Elastic Image Configuration page, but it makes no mention of the Bamboo VM user or password and I'm not seeing it anywhere else.
Thanks for the help!
Thanks for following up! I was able to reset the password, run prepareInstanceForSaving.bat and create a new AMI. However, the Elastic Agent on the new AMI never leaves the "Pending" state and is therefore unable to start any builds.
I tried this many times to get it to work with no luck, here's my steps to reproduce:
1. Start Default Image EBS x86_64 (windows) (stock image) VM (ami-976edafe) via Bamboo
2. Login as Administrator
3. Change Bamboo user password
4. Set Ec2SetPassword to Enabled in C:\Program Files\Amazon\Ec2ConfigService\Settings\config.xml
5. Run C:\opt\bamboo-elastic-agent\bin\prepareInstanceForSaving.bat
6. Shutdown VM
7. Create new AMI from VM
8. Update Elastic Image Configuration with new AMI ID
9. Start VM with new AMI.
10. Wait for Elastic Agent status to go Idle
I also tried running prepareInstanceForSaving.bat as the Bamboo user as well.
The agent on the original AMI (ami-976edafe) typically starts after about 10 minutes or so. However, after the steps above, the agent on the new AMI wouldn't start (waited 30 minutes).
Am I missing any steps?
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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