- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Make sure your API gateway account is migrated to use the UsagePlans feature.
In our case, the AWS console was unaware of it and just assumed it was enabled. But it wasn't.
To check your account supports usage plans, execute
> aws apigateway get-account
Check for features, it should include UsagePlans item.
If it's not there, execute
> aws apigateway update-account --patch-operations op='add',path='/features',value='UsagePlans'
This will also create default usage plans, and you may need some cleanup because duplicated usage plans are not allowed.
The API Gateway console doesn't seem to correctly handle the REST apis. If you perform the following the CLI
aws apigateway get-api-keys shows
you'll see that the keys are missing configuration for stageKeys
"stageKeys": []
You can set this using the CLI
aws apigateway update-api-key --api-key {KEY_ID} --patch-operations op='add',path='/stages',value='{API_GATEWAY_ID}/{STAGE}'
The change will take up to 5 minutes to apply (usually shorter)
AWS is such crap. There is always some BS thing like this that is completely obscured in the console and wastes hours of dev's lives.
This solved the problem for me. I set up a new API Gateway in eu-west-1 for the first time (having previously had no problems in us-east-1 and us-east-2) - despite setting up everything in an identical manner, the UsagePlans item was missing in eu-west-1. Thank you for your comment!
Life save. After several hours hair-tearing I found this. I had to delete my existing usage plan, and API key and then recreate them before it kicked in. Thank you