I'm having a frustrating issue with my API gateway. Whenever I make a GET request, it's throwing an error saying a required request parameter is missing. I've removed the parameter requirements and redeployed the gateway to the stage, but the error persists. I've even deleted the GET request entirely and redeployed, yet it's still bringing up the missing parameter error in Postman as if the original gateway exists. I also noticed the clear cache button in the staging area is greyed out. Even when I try to recreate the GET method, it still points to the old one. It feels like this API is stuck in some weird state despite what AWS shows. Any ideas on what might be going wrong?
4 Answers
This sounds like a classic layer 8 issue, aka user error. Just double-check the specific API stage you’re editing. If you’re making changes to the wrong one, that could explain the continued errors. Knowing you’ve only got one stage helps narrow things down, but double-checking is key!
It seems like there might be a mix-up with the type of API you’re working with. If you’re using REST APIs, make sure you deploy those changes to the right stage because they won’t auto-deploy like HTTP APIs do. You could be updating it but not seeing those changes applied.
If it's still not working, try reaching out to AWS support. They might have insights into what's going wrong on their end, especially if it seems like the system isn't reflecting your changes accurately.
Have you considered the possibility of a caching issue? Sometimes, creating a new stage and redeploying there can help clear out any old configurations causing the problem. Also, check whether your Lambda functions or integrations might still be holding onto outdated parameters. If this keeps happening, checking via the AWS CLI or SDKs could reveal more info since the console can lag a bit.
I’ve been on the same stage for a week with no changes to the error message. Definitely scratching my head here!