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

An error occurred (UnrecognizedClientException) when calling the PutIntegration operation: The security token included in the request is invalid #198

Open
avengerpenguin opened this issue Jul 26, 2016 · 5 comments

Comments

@avengerpenguin
Copy link

I get this error randomly part-way through the "Creating API Gateway routes (this only happens once)" stage.

I'd tried a few things and it seems to fail somewhere between 8% and 11% through, which suggests to me that it's not doing the same operation. In fact, on one run it failed on "PutMethodResponse" and not "PutIntegration"

The only thing I can conclude is there is some kind of rate-limiting I'm hitting that Zappa is seeing as key issue, but key pair worked fine for the first 8-11% of the operation.

I can't see a way to "resume" the API Gateway part as it's part of the first-time "zappa deploy" command. That would give me a workaround here at least.

@avengerpenguin
Copy link
Author

I found a workaround by limiting the parameter_depth and http_methods config values to precisely what I need (thus limiting the number of put actions on the API Gateway api). The progress bar moved much more quickly and finished before any error could occur.

@avengerpenguin
Copy link
Author

Of course, there's still a bug or weird behaviour here if I had wanted to use deeper URLs and more methods.

@Miserlou
Copy link
Owner

I haven't encountered this, and it looks like a bit of a bastard to reproduce, but leaving this ticket open for now.

API Gateway path creation needs a real overhaul any, I'd much rather do it using something like troposphere and CloudFormation if possible, doing it one API call at a time is awful. API Gateway didn't used to be available in CF, I don't know if that's still the case.

@avengerpenguin
Copy link
Author

I assume the code has changed enough now that I could have a check again to see if this still happens?

@Miserlou
Copy link
Owner

Miserlou commented Dec 6, 2016

I can look into this if you have a way to reproduce, otherwise I can't really do anything about it. We are using CF, so this may not even be relevant. Checks would help though..

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

No branches or pull requests

2 participants