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

[Migrated] Created API Key is not associated with a Usage Plan #52

Closed
jneves opened this issue Feb 20, 2021 · 0 comments
Closed

[Migrated] Created API Key is not associated with a Usage Plan #52

jneves opened this issue Feb 20, 2021 · 0 comments

Comments

@jneves
Copy link
Contributor

jneves commented Feb 20, 2021

Originally from: Miserlou/Zappa#390 by jakul

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

[2b4492] [2016-10-11 15:26:57] Verifying Usage Plan for request: 25bdd356-8fc7-11e6-93c4-e3cf41861839. API Key: **********************************gE96dR API Stage: i01t0vftre/staging
[2b4492] [2016-10-11 15:26:57] API Key **********************************gE96dR not authorized because method 'GET /' requires API Key and API Key is not associated with a Usage Plan for API Stage i01t0vftre/staging: API Stage is not in a Usage Plan
[2b4492] [2016-10-11 15:26:57] Method completed with status: 403

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)

@jneves jneves closed this as completed Feb 20, 2021
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

1 participant