Cisco Umbrella got errors when it called GetBucketLocation

[Jian_Zhang]

Some of the Cisco Umbrella integrations got an error when they called 'GetBucketLocation' at this line: beats/x-pack/filebeat/input/awss3/input.go at 8ea54119e556fe9de613b7f15a14dbfdd2f31f84 · elastic/beats · GitHub

[elastic_agent.filebeat][error] Input 'aws-s3' failed with: failed to initialize s3 poller: failed to get AWS region for bucket: operation error S3: GetBucketLocation, exceeded maximum number of attempts, 3, https response error StatusCode: 0, RequestID: , HostID: , request send failed, Get "//cisco-managed-us-east-2./amazonaws.com/cisco-managed-us-east-2?location=": unsupported protocol scheme ""

Someone said 'us-east-1' is more reliable, but the source code does not make sense to me that bucket name with other region would break. This issue has not been seen yet in other integrations with S3.

Did anyone have similar issues before?

[leandrojmp (Leandro Pereira)]

//cisco-managed-us-east-2./amazonaws.com/cisco-managed-us-east-2?location=

This seems to be wrong, how does your configuration looks like in the integration?

[Jian_Zhang]

Thanks for the reply. Nothing particular in those failed integrations:

Bucket ARN: arn:aws:s3:::cisco-managed-us-east-2
Bucket Region: 'us-east-2'
Bucket List Prefix: <just a string>
Number of Workers: 1
Endpoint: amazonaws.com

Other optional inputs are blank. I don't see anything different from the configs that work. Access key ID and secret key look correct. Is it possible that the secret key is expired?

[Jian_Zhang]

Bump. I've got 4 cisco umbrella integrations that hit the same error, but their configurations are not different from any other successful configurations. Any thoughts?