Elastic Bamboo EBS Client.AuthFailure: Not authorized for instances: [i-XXXXX]

Hi,

Atlassian has uploaded our certs to Bamboo, and I am trying to set up EBS to help our maven builds.

When i run createInitialVolume.sh 6, i get the following Client Auth error..
mountLocation: /mnt/bamboo-ebs
attachedDeviceLocation: /dev/sdh
instanceId: i-XXXXXX
amiId: ami-XXXXXXXX
availabilityZone: us-east-1a
Creating volume with size 6 GB...
Waiting for volume vol-XXXXXXXX to start up...
Waiting while volume vol-XXXXXX is creating...
Attaching volume vol-XXXXXXX
Client.AuthFailure: Not authorized for instances: [i-XXXXX]

I can see the mounted drive , and upload my maven repo, but when I generateSnapshot..

generateSnapshot.sh
mountLocation: /mnt/bamboo-ebs
attachedDeviceLocation: /dev/sdh
instanceId: i-XXXXXXX
amiId: ami-XXXXXXX
availabilityZone: us-east-1a
No volume attached

It says no Volume attached, and the snapshot is not visible in AWS console. The volume is, but when I make a snapshot though the AWS the elastic instance cannot mount the snapshot.

Any ideas?

4 answers

1 accepted

Our Bamboo key was out of sync with the AWS account settings.

0 vote

I can see the mounted drive

What does ec2-describe-volumes say at that point? Does it list your instance and the volume?

[root@domU-12-31-39-0E-B2-11 bamboo-ebs]# ec2-describe-volumes
VOLUME vol-1c3f3e73 6 us-east-1a available 2012-05-14T10:54:08+0000

Hmm, it only says 'available' on the volume, not 'attached', which is a prerequisite for mounting the EBS. What do you mean by 'I can see the mounted drive'? What does 'mount' say?

I mean I can cd to /mnt/bamboo-ebs and copy files there, also under /maven there is the m2 repo which I can populate with uploaded files.

[root@domU-12-31-39-02-5D-B1 ~]# mount
/dev/sda1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda2 on /mnt type ext3 (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/mnt/home on /home type none (rw,bind)

I also cant see the running instance in the EC2 console, although I can see the EBS volume created by the script in the console.

ec2-describe-instances also gets a client auth faliure.

[root@domU-12-31-39-02-5D-B1 ~]# ec2-describe-instances i-93e89cf5
Client.AuthFailure: Not authorized for instances: [i-93e89cf5]

Then..

[root@domU-12-31-39-0E-B2-11 /]# generateSnapshot.sh
mountLocation: /mnt/bamboo-ebs
attachedDeviceLocation: /dev/sdh
instanceId: i-57c34a31
amiId: ami-395a8550
availabilityZone: us-east-1a
No volume attached

[root@domU-12-31-39-0E-B2-11 bamboo-ebs]# ec2-describe-volumes
VOLUME vol-1c3f3e73 6 us-east-1a available 2012-05-14T10:54:08+0000

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
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

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...

1,316 views 0 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