Bamboo Server reseting security on cipher folder

I installed and ran the Bamboo Server. With an evaluation key. Once it is running I make it to the Create New Plan. Enter my information for my Bitbucket Cloud. Test the Connection and it passes. When I submit the "Configure Plan" button I get this wonderful message:


After doing some research and finding only two relevent links. I began the process of adjusting my user privilages including running everything from Administrator to no avail. 

I discovered that if I change the cipher folder permissions, then restart the computer. The cipher folder's security stays correct.


I can access the folder normally.


Now when I attempt to create the Configure Plan again. I recieve the same java.nio.file exception and the folder's security is reset, and does not work correctly. Bamboo seems to reset, or trigger reseting, the security on this folder.




Again I have tried from User, Administrator, etc... nothing works. Bamboo keeps throwing that error, and the cipher folder keeps reseting it's permissions.


Is this a Bamboo bug? How do I fix it?

Please help.

3 answers

1 accepted

It was indeed permissions related. The type of software we are building requires strict user privlages on our machines.

So to correct the problem. I had to run an EC2 instance on AWS. Then setup a Bamboo Server on that instance. That gave me Administrator rights. and allowed Bamboo Server to correctly write the data to the cipher folder.

1. Setup Bamboo Server Instance
* Services(dropdown) -> EC2 (under Compute)
a. Click "Launch Instance" Button
b. Step 1
- Select "Microsoft Windows Server 2013 R2 Base"
c. Step 2
- Select "General purpose" t2.micro (free tier eligible)
d. Step 3
- leave defaults
e. Step 4 - Add Storage
- leave defaults
f. Step 5 - Add tags
- leave default
g. Step 6 - Configure Security Group
- Under "Assign a security group"
- Select "Create a new security group"
- Leave default: Should give an RDP, TCP, Port and Source:
- Set up any necessary password/creds
h. Review and Launch
2. Once Instance is up and in a running state
a. Select "Instances" on the left menu
b. Select the newly created instance
c. Add a name to the Instance as Bamboo Server
d. With the Bamboo Server Instance selected, click the Actions dropdown and select "Get Windows Password"
*NOTE: you can only do once, so save the information
e. Using the PEM file we saved earlier. Retrieve your password.
c. With "Bamboo Server" selected, look in the Description tab on the right by "IPv4 Public IP"
d. Copy this IP Address



1. Launch "Remote Desktop Connection" program
a. Paste in the IPv4 Address
b. Login using the password we retrieved above.
c. The EC2 Instance should now be running (Our Bamboo Server Instance)

2. Setup AWS CLI
a. Goto: in a web browser on your Bamboo Instance
b. On the right, select the 64-bit or 32-bit Windows installer
c. Follow the instructions and install

3. Install Java Run Time
a. Goto:
b. Click on "Windows Offline (64-bit)" (or "Windows Offline" if not on a 64 bit system)
c. Follow the instructions to install
d. Once installed, hit Start and type environment - the search should give you "Edit environment variables for your account"
e. Click on this link
f. The "System Properties" dialoge should appear
g. Click "Environment Variables..." at the bottom
h. Setup you Java variable
- Under "User variables for Administrator"
- Click the "New" button
- Type in JRE_HOME
- Type in the location of your Java installation
- Example: C:\Program Files\Java\jre.8.0_144
*NOTE: if you installed a version different than the RUN TIME ENVIRONMENT then you will use JAVA_HOME instead and provide the location of the Java installation
- Click "OK"
- Click "OK" again

4. Install Bamboo Server
a. Open a web browser and goto: sc
b. Click the "Get started for free" button
c. Follow the instructions and install
*NOTE: Make sure to install to the default locations
- That will put a Bamboo folder in Programs (x86)
- It will put a bamboo-home folder under your user

5. Setup project. You will need to get an "evaluation" key
6. You should be at the "Create Plan" page
a. Add your repository information.
- Name must be the name of the repository
- Then your username and password you use to log into Bitbucket
- Click "Load Repositories" and select the required repo
- Test connection to ensure it is working correctly
- Click "Save repository" button.
b. ! Make sure to check the Enable plan !
7. Finish/Save the Plan config. We'll come back and finish the task setup later.
8. Setup your global variables
a. In your Bamboo Administration page (click the gear and select overview)
b. Select "Global variables" on the left
c. We want to add two new variables:
Variable name Value
awsAccessKey <access key from your dedicated codedeploy IAM>
awsSecretAccessKeyPassword <secret from your dedicated codedeploy IAM>
*NOTE: make sure the variable name is spelled as shown above
9. Setup Shared Credentials to access AWS
a. On the main left hand menu select "Shared credentials"
- click "Add new credentials"
- Use the same name you use for you Dedicated CodeDeploy IAM
- Insert your awsAccessKey from above
- Insert your awsSecretAccessKeyPassword from above

You can now setup your Artifacts, or go which ever direction you need to for your project.

0 vote

Hi Jeremy,

There is a Communities post titled Bamboo cipher keys are seemingly not generated that may help.  Take a look at Kiran01BM's post.  The resolution was as follows:

The Bamboo service was running as a Local System user (This happened by default when installing Bamboo using the .exe installer option. Whereas with Bitbucket installer the service was installed with a separate service account which had adequate permissions) which did not have access to bamboo-home\xml-data\configuration\cipher. To fix this I just used created a seperate account with Full  Access permissions to the file-system and configured Bamboo service to run as this user.

Make sure your setup is the same and see if you get different results!



Thank you for the answer. Unfortunately our security requirements do not allow me to create a separate account on our system. I had seen this previously, and it led me to updating, what I could, of our user privlages. But that still did not correct the issue.

Thanks for the reply.  Let us know what the issue ended up being when you figure it out on that end.

I did not find a solution to my problem. But, I do now know it is in regards to our system's user privlages. It is not a Bamboo bug.

What I ended up doing was creating an EC2 instance on AWS, installing Bamboo and it works just fine there.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

2,022 views 1 5
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you