Why is Elastic bamboo-agent-release-us-e1 in US-EAST-1 pulling from an S3 bucket in US-WEST-1?

[David Andrews]

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/54.231.236.32] 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/52.219.24.32] failed: connect timed out

[Przemek Bruski · Accepted solution]

This is a bug in AWS SDK. It has been fixed in the version we shipped with 5.15.

[David Andrews]

Thank you!

[David Andrews]

I updated to 5.15.5 and everything works like a charm.