Having some real issues with APIGW, custom domain and mappings, I will be so grateful if someone knew where I was going wrong: https://stackoverflow.com/questions/78303514/aws-api-gateway-custom-domain-name-with-mapping-and-proxy-route-based-on-path
It’s sometimes forbidden response, and sometimes not found depending on what variation of mapping path/api route I try.
Adding a $default does catch it, however, that defeats the point, I am trying to make one gateway for multple services based on the path (i.e. /account).
have you deployed the API to a stage?
Yep.
It’s APIGWV2. HTTP API with auto-deploy turned on if that’s any help.
As I mentioned above, adding the $default route to the APIGW does trigger the Lambda and I get a response, but that’s not what I need, I need the /account as a route so that I can route to each service.
