why does api gateway with http api using api mapping fail with 404?

0
votes

I have a custom domain name in AWS API gateway. I am using the same domain for 2 separate API stages. One API stage is REST API, and the other HTTP API.

When I test out my setup, everything works for the REST API. However, the mapping path for HTTP API is not working and I get status-code = 404 Not Found, with 0kb body.

references used: https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-mappings.html https://docs.aws.amazon.com/apigateway/latest/developerguide/rest-api-mappings.html

api mapping configuration

From my testing in postman, i get the following result when calling the custom domain.

 1. {{api.gateway.custom.domain.url}}/foobar - works
 2. {{api.gateway.custom.domain.url}}/this-no-work/foobar - 404
 3. {{api.gateway.custom.domain.url}}/this-works/foobar - works

does anyone know why (2) gives 404? api-gateway REST API with mapping works while api-gateway HTTP API will return 404 with 0kb body. Is there something I am missing?

note: the (none) path mapping has been added for a sanity check, and I was able to get the expected response.

1
amazon-web-servicesaws-api-gateway

1 Answers

0
votes

when default endpoin is created in my case it uses this pattern

https://{api_id}.execute-api.{region}.amazonaws.com/

an answer might be: Disable the default endpoint for an HTTP API

more details here https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-disable-default-endpoint.html