-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Created API Key is not associated with a Usage Plan #390
Comments
This looks like it wouldn't be that hard to do. I wasn't familiar with Usage plans when i implemented the api key portion. I'll see what I can do to add this feature. |
Any update on this? |
I have also had troubles with this issue. As it is now, api key authentication won't work unless the user manually creates a user plan in Amazon Gateway API and links the API and the Key. |
For those, like me, that were waiting for a fix, here is a temporary workaround. It will create the usage plan and link the api key to it via a Zappa post script.
Then add the following to your zappa settings. This assumes that you have the code in a file called "zappa_post.py" in the same directory as zappa_settings.
Largely based on romabysen's response on #707. |
I have "Usage Plans" enabled on my AWS API Gateways and now when I create a new API with Zappa which has
api_key_required: true
all requests I make to that API return 403.Apparantly AWS requires created API Keys to be associated with a usage plan before they can be used
I can associate the keys manually in the AWS UI for now, but ideally Zappa should auto create the usage plan for me (or allow me to specify the name of an existing usage plan to associate the key with)
The text was updated successfully, but these errors were encountered: