Lambda Deploy

[rbgfloripa]

Hi all,

Is there any way to deploy the application in an aws lambda WITHOUT Architect?
Because my deployment process is completely separate and automated. I don't have access to the AWS account.
I think I would have to generate a ZIP file of the application to run in a lambda or something like this.

Thanks.

[rbgfloripa]

I've tried it in several ways with no success.
I'm stuck with this problem and can't move forward.
I will probably need to abandon the idea of ​​using remix in this project.

[vinarius]

same, nearly 2 years later :(

[MattyBalaam]

I’m in a similar situation. I want to bring in Remix to our stack, which in terms of frontend apps is currently PWA hosted in S3 and our company is going to be staying AWS for quite a long time. I personally need a bit of hand holding around how to use edge computing in AWS, and would rather not need to briing in yet another dependency (Architect) if I can help it.

I see there is something called lambda@edge - would this be the correct thing to look into? https://aws.amazon.com/lambda/edge/ Or are the simple Cloudfront Functions the way to go? https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/edge-functions.html

[rbgfloripa]

I'm trying to run the application on a simple lambda for now.

[thomasfr]

Have you been successful in running it on Lambda? If yes, what did you need to do?

[devraj]

I have been wanting to achieve the same thing without adding another dependency like Architect. We use a Kubernetes (deployed using Terraform) based setup which provides us some options:

• Deploying Remix apps to Kubernetes?
• Found this discussion which provides a links to Deploying Remix to Kubernetes written by @chikamichi
• @BenMcH maintains the techno-stack while I wont' want to buy into the stack it will be well worth looking at how it's been put together.

We work with Python on the server and have PWAs at the moment, which I am looking to replace with remix based apps

[BenMcH]

Hi, thanks for the shout out but I haven't been working on Web apps recently, so the techno stack is woefully out of date. The kubernetes deploy files are there though and should still work 🙂

[devraj]

Also tagging this issue reported by @nicolaserny
#4176

[fones]

Hi guys, did someone tried to use custom lambda container image for this? @rbgfloripa @devraj

You can deploy lambda as docker image with some limitations. https://docs.aws.amazon.com/lambda/latest/dg/images-create.html

[thomasfr]

It’s this project: https://github.com/awslabs/aws-lambda-web-adapter

[fones]

@thomasfr and you deploy remix with success?

[thomasfr]

Yes! We use it at AWS internally

[thomasfr]

But you don’t have to use docker to use the Lambda web adapter. You can also use it without docker. Alternatively, you can also do the Request Handling in the entry.server.ts file. But the LWA makes that unnecessary.

[jarimustonen]

@thomasfr Would it be possible to have a bit more in-depth instructions? I noticed that there are lot of examples but Remix and Remix in ZIP are missing. Also, it would be great if the example would use Vite as Remix is in the process of migrating to Vite.

Edit: I went and added an issue for this: awslabs/aws-lambda-web-adapter#387

As you are using it internally, it would really make sense to also embrace this externally.

[mogadanez]

here is exampe:
https://github.com/shamsup/remix-starter-serverless
it still uses
import { createRequestHandler } from "@remix-run/architect";

but not full architect package

you can inspire how createRequestHandler looks like and migrate it to your codebase

[gotgenes]

This project uses a version of Remix that predates the current Vite architecture, which became the default in v2.7.0.

I found relevant discussion at #8836.