2 Answers
- Newest
- Most votes
- Most comments
1
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)
answered 4 months ago
0
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.
answered 2 months ago
Relevant content
- Accepted Answerasked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago