I have my elastic agent using a VPC endpoint in us-east-1. That is the only S3 access that it has, due to proxy and security conditions. VPC endpoints are not cross-region. Why is the bamboo-agent-release-us-e1 trying to reach to an S3 bucket in us-west-1? This is causing my agent to fail to pull from that S3 bucket. Here is the relevant error:
[AmazonClients] Unable to get bucket location for [bamboo-agent-release-us-e1], using default. Error: com.amazonaws.AmazonClientException: Unable to execute HTTP request: Connect to bamboo-agent-release-us-e1.s3-us-west-1.amazonaws.com:443 [bamboo-agent-release-us-e1.s3-us-west-1.amazonaws.com/18.104.22.168] failed: connect timed out
INFO [main] [ElasticAgentSynchroniser] Downloading agent file list from s3://bamboo-agent-release-us-e1/5.14.1/295e95c11ead6d50fef7b824ed1f62dd10c5972c/assembly.list
Exception in thread "main" com.amazonaws.AmazonClientException: Unable to execute HTTP request: Connect to bamboo-agent-release-us-e1.s3-us-west-1.amazonaws.com:443 [bamboo-agent-release-us-e1.s3-us-west-1.amazonaws.com/22.214.171.124] failed: connect timed out
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot