Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Magpie S3 discovery is impossible in US_EAST_1 and AWS_GLOBAL regions #183

Closed
belosh59 opened this issue Jul 23, 2021 · 0 comments · Fixed by #184
Closed

Magpie S3 discovery is impossible in US_EAST_1 and AWS_GLOBAL regions #183

belosh59 opened this issue Jul 23, 2021 · 0 comments · Fixed by #184
Assignees

Comments

@belosh59
Copy link
Contributor

We are getting the following exception while discovering S3 buckets in mentioned regions.
Exception received:

magpie_1   | 17:43:04.604 [pool-1-thread-1] ERROR i.o.m.p.a.d.AWSDiscoveryPlugin - Discovery error  in aws-global - software.amazon.awssdk.services.s3.model.S3Exception: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'ap-northeast-1' (Service: S3, Status Code: 400, Request ID: 36Y2XG2XWY39ZJ9D, Extended Request ID: GyLAoH67aJl2Yv1T3ff0vGYndLSh/uuDeUOhUEpbWMJrRPecxvk6dztR4tNg6sM1V8sVc7AN+Rs=)

Nevertheless for other regions we are able to list all buckets in various regions.
Related readings:
aws/aws-sdk-cpp#1339
aws/aws-cli#3864
aws/aws-sdk-net#323
aws/aws-sdk-go#3115
aws/aws-sdk-go#380

@belosh59 belosh59 self-assigned this Jul 23, 2021
@belosh59 belosh59 modified the milestone: 1.0 Jul 23, 2021
@belosh59 belosh59 linked a pull request Jul 23, 2021 that will close this issue
belosh59 added a commit that referenced this issue Jul 29, 2021
…overy

#183 Fix S2 discovery failure in US_EAST_1 and AWS_GLOBAL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant