Deploying on AWS - Umbrella thread #1106
ennioVisco
started this conversation in
General
Replies: 1 comment 1 reply
-
@pi0 is this thread anyway useful for you and the development team? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Being AWS a fairly general cloud service, there are several ways to deploy on it:
Packaging Nitro in Lambda-compatible functions & expose via API Gateway
It involves the usage of the current
aws-lambda
preset to build the functions, as described in https://nitro.unjs.io/deploy/providers/aws, and is a bit far from zero-config, as it still requires setting up:Packaging the Nitro-based app for static hosting:
Of course, another option when possible for the application that is using Nitro, (e.g.
nuxt
or otherunjs
-based apps), is the application can be pre-rendered as static web assets (html
,css
,js
, ...) and deployed to an AWS. To set it up one has to:Nitro could deal with this case systematically, as proposed for Vercel (#818).
Packaging Nitro for CloudFront's Lambda@Edge
Just like Vercel's edge functions, Lambda@edge allows the developer to achieve better performance by exploiting a leaner runtime + a CDN-based caching.
A proposal for an edge-based preset is available here (https://github.com/unjs/nitro/pull/1075/files) in response to the related issue #79.
Amplify-based deployment
Amplify is a minimal-code frontend for configuring AWS services. It typically delivers one of the three previous options, although it scaffolds the services automatically based on a few input configurations from the developer.
It does not currently provide a guide for Nuxt 3, although it does for Nuxt 2.
I would leave this as a last-resort option for the moment, though, as it is still very rigid in terms of configurability (e.g. it does not allow to use Github action instead of AWS's built-in solution).
Related issue: #80
CI/CD & docs
It would be nice to provide CI/CD examples as Github actions/ CodeBuild specs, as well as to extend the docs to guide the developers in the deployments
Beta Was this translation helpful? Give feedback.
All reactions