- 최신
- 최다 투표
- 가장 많은 댓글
Hi, since you didn't create any stage, that means that you're the default stage '$default'. The route that you configured isn't correct and you need to set the route to $default and add the integration to your webservice endpoint like http://webservice_url
To rectify this, first delete all the existing routes and then follow these steps:
- Go to your API Gateway and select Route
- Click Create
- Leave the Any method as is and type in the path $default without a leading slash.
- Click on Attach integration and select your webservice endpoint
Eventually, this is how it should look like:
Routes:
Integrations:
Hi,
{"message":"Not Found"} is technically an HTTP 404 status code. It looks like the API Gateway routing isn't set correctly, meaning that you're trying to fetch an item that doesn't exist in the requested path or you're using incorrect path in the requested URL.
Can you provide some details on what the API gateway routing and stages look like?
Also what's the URL path that you're using when hitting the API gateway?
- This can also happen if you have "Default endpoint" set to
Disabledand are not using a custom domain to access the API. - I also later had this happen from my backend rerouting to add an ending slash to my route and API Gateway treating that as a separate endpoint... This was hard to notice it was even happening. Best fix for me was to stop the reroute on my backend.
관련 콘텐츠
AWS 공식업데이트됨 2년 전- AWS 공식업데이트됨 일 년 전
Hello
When we created the API Gateway we didn't specify any stage. It was left to AWS to decide which stage to be used.
As for routes, we tried using the following and none of them worked.
/ GET / ANY {proxy+}
the URL that we're using on our clients is:
https://api_gateway_url/req11.json
In our testing we used Postman and Curl and both are showing the same result.