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

Bucket region issue when Lambda triggers #22

Closed
rjlupinek opened this issue Nov 22, 2019 · 3 comments · Fixed by #26
Closed

Bucket region issue when Lambda triggers #22

rjlupinek opened this issue Nov 22, 2019 · 3 comments · Fixed by #26
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@rjlupinek
Copy link

rjlupinek commented Nov 22, 2019

When the Lambda triggers it looks like I am getting an error due to the region I deployed my infrastructure.

failed to upload report to bucket: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-east-2' status code: 400, request id: BC04B1B8AED32969, host id: Cx3IjHtCIrQnS0wX

I set everything to build in us-east-2. I am going to see if I cannot correct this by moving my S3 bucket for inventory to us-east-1 as I suspect that is the issue.

@rjlupinek
Copy link
Author

rjlupinek commented Nov 23, 2019

I confirmed changing region to us-east-1 from us-east-2 for all resources corrected the issue. I now have an inventory file.

@briankfitzwater briankfitzwater self-assigned this Nov 26, 2019
@briankfitzwater briankfitzwater added the bug Something isn't working label Nov 26, 2019
@briankfitzwater
Copy link

@rjlupinek
Copy link
Author

Hey team. It looks like you gentlemen were correct on our last call. When switching the order of regions the first region is assigned the default. We swapped it and go this error:

21:19:39
failed to upload report to bucket: BucketRegionError: incorrect region, the bucket is not in 'us-east-2' region at endpoint '' status code: 301, request id: , host id: : errorString null
failed to upload report to bucket: BucketRegionError: incorrect region, the bucket is not in 'us-east-2' region at endpoint ''
	status code: 301, request id: , host id: : errorString
null

Let me know if you want to setup a test session.

@briankfitzwater briankfitzwater added documentation Improvements or additions to documentation and removed bug Something isn't working labels Nov 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants