unable to run elastic agent on ec2

Starting Elastic Bamboo Agent...
2016-09-28 09:44:01,037 INFO [main] [S3Sync] Syncing from: bamboo-agent-release-eu-w1/5.12.4-D20160704T134120/aa02e30788f7683b8f5431d112a3a6dec65b44065b68d45b46c102a9452b0435/ to /opt/bamboo-elastic-agent
2016-09-28 09:44:01,931 INFO [main] [S3Utils] Syncing s3://bamboo-agent-release-eu-w1/5.12.4-D20160704T134120/aa02e30788f7683b8f5431d112a3a6dec65b44065b68d45b46c102a9452b0435/ to /opt/bamboo-elastic-agent
2016-09-28 09:44:01,932 INFO [main] [S3Utils] Fetching the list of remote objects...
Exception in thread "main" com.amazonaws.services.s3.model.AmazonS3Exception: The AWS Access Key Id you provided does not exist in our records. (Service: Amazon S3; Status Code: 403; Error Code: InvalidAccessKeyId; Request ID: 72F202E6F5976F8C), S3 Extended Request ID: gXK2kUXjx9Fj2yTyWjQoJbo+JUT6MpmYiYWNX5jLZdIxnXcePBhd4GHVFofAy7ODg0xrTve4hBc=
at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1077)
at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:725)
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:460)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:295)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3714)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3664)
at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:637)
at com.amazonaws.services.s3.AmazonS3Client.listObjects(AmazonS3Client.java:620)
at com.atlassian.aws.s3.S3Utils.getObjectNamesAndHashes(S3Utils.java:353)
at com.atlassian.aws.s3.S3Utils.sync(S3Utils.java:161)
at com.atlassian.bamboo.agent.elastic.S3Sync.sync(S3Sync.java:72)
at com.atlassian.bamboo.agent.elastic.installer.ElasticAgentInstaller.main(ElasticAgentInstaller.java:66)

 

We're blocked on it, so please help!

4 answers

1 vote

There was a problem with our public access key that has been solved right now.

 

Please re-try and confirm everything is now working fine. In case it is not please log a ticket in support.atlassian.com

 

Best Regards,
Dario.

Same here - started a few hours ago.

We are accessing a slightly different URL probably because we have a slightly different version of Bamboo

s3://bamboo-agent-release-ap-se2/5.9.4/d153c59bdd74a7e5b1899a715b7880f2b147b784/

This is blocking a team of developers. Please resolve this immediately!

I was able to resolve it by upgrading the bamboo-agent that is installed on our AMI. It probably doesn't happen with Atlassian's Stock AMIs.

https://confluence.atlassian.com/bamboo/creating-a-custom-elastic-image-linux-296093037.html

Just follow the steps at "5.3.2 Downloading agent installer to the instance" to upgrade.

0 votes

This was an infrastructure issue on our side. Everything should work correctly now.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 8 hours ago in Jira Ops

Jira Ops Early Access Program Update #2: Let’s talk severity levels

Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...

20 views 0 0
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