hono aws lambda 404 issues
I found hono while doing to experimenting with better-auth js and have been testing with it recently. I want to build a hono API in aws lambda for my projects so I can pay per usage instead of provisioning a server to start.
I am running into an issue where I am receiving a 404 code back from my API gateway, although the lambda function is being hit with what I assume is the correct path. Although I guess it can't be if I am getting a 404? Anyway, I am attaching the github repo for the AWS CDK build.
I am hoping someone can help me figure this out? Please message me if you have run into something similar. Some AI suggested solution mentioned that the stage of the API gateway might be the issue. Basically the "prod" in https://xxxx.execute-api.us-east-1.amazonaws.com/prod/some-path could be getting in the way of the path hono is looking for? I wasnt able to find a solution to this issue though, and when i tested adding the "/prod/..." to the app.get() argument, I still got the 404.
Again, any help is appreciated! Below is the GitHub repo with my testing code:
https://github.com/leocucinell/aws.hono-serverless-rest-api
GitHub
GitHub - leocucinell/aws.hono-serverless-rest-api
Contribute to leocucinell/aws.hono-serverless-rest-api development by creating an account on GitHub.
7 Replies
is
/* even a valid path? (I am actually asking, I am not saying it is wrong)
I am hoping someone can help me figure this out? Please message me if you have run into something similar. Some AI suggested solution mentioned that the stage of the API gateway might be the issue. Basically the "prod" in https://xxxx.execute-api.us-east-1.amazonaws.com/prod/some-path could be getting in the way of the path hono is looking for? I wasnt able to find a solution to this issue though, and when i tested adding the "/prod/..." to the app.get() argument, I still got the 404.PS: when you want to have a prefix on all your routes, you can simply do
new Hono().basePath("/prod")
--
are you able to view logs from your hono app in aws?
and have you added the hono logger as middleware?
I'd investigate that if I were you, where does the 404 originate from? hono or aws?
if it is from hono, then your basePath is configured incorrectly
which would be easy to see by looking at the logsthe 404 originates from hono. Since the lambda function is being triggered, the ApiGateway + lambda are configured correctly.
the path "/*" is valid in express and I might have just lazily transferred my knowledge over. Ill dive deeper into the hono docs to verify. I did test with multiple other paths ("/", "/test", etc...) and all returned 404s.
I think you might be in the right direction with the hono basePath. I will test and let you know.
Thanks for responding!:hono:🤘
https://hono.dev/docs/api/routing#basic
Yes it looks like the woldcard routing works in hono!
Routing - Hono
Web framework built on Web Standards for Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Node.js, and others. Fast, but not only fast.
What's the benefit of
/* over *?I believe they are the same, I just like the syntax of the slash better
Also I tried the .basePath("/prod"), didnt seem to work 🥲
Going to try some other ideas I read online and will update findings here!
Did you look at the logs?
(after adding the hono logger)
Oh my gosh. I had app.get() and was using the wrong method.
yikes... can't believe I did that 😅
Thanks for answering my post @Arjix !
I obviously still have much to learn about hono, I will be adding the logger and seeing what I can do!
I obviously still have much to learn about hono, I will be adding the logger and seeing what I can do!