Load
Explore posts from serversBABetter Auth
•Created by Load on 4/4/2025 in #help
Hono API on Lambda
Has anybody ever made a hono API connecting to better-auth deployed on AWS Lambda. I have tried following the documentation and am getting 404s on all routes associated with better-auth. I am at a loss here and would love to see a working example if anyone in the community is willing to share!🙏
2 replies
BABetter Auth
•Created by Load on 4/2/2025 in #help
Hono + Better-auth + Lambda Cookies
I am wondering if anybody has set up an API on AWS Lambda using hono secured with Better-auth. I have used Better-auth in the past for a Next.js project, I am now exploring how to use it with Hono and I would like to deploy it in a serverless environment to start (AWS Lambda). Does anyone have experience with Cookies management in this context? Next.js used to just take care of it for me, but now I am having to return the cookies to the frontend, React app, which get stored and sent with subsequent requests. However, when I try to do an auth.api.getSession() api call and pass the headers into it, I am getting null.
I will provide any code I have for this discussion. Going to be at work for the next few hours so I appreciate anyone who joins ins patience! 🍪 🍪 🍪
12 replies
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
14 replies