amplify-hosting
sst
amplify-hosting | sst | |
---|---|---|
20 | 179 | |
440 | 20,214 | |
0.0% | 1.7% | |
6.7 | 9.8 | |
2 months ago | 1 day ago | |
Dockerfile | TypeScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
amplify-hosting
-
Create a simple OTP system using AWS Serverless services
Amplify Web Hosting
-
How to Deploy a Next.js 13 App to AWS with Amplify Hosting
AWS Amplify Hosting - the ultimate solution for fast, secure, and scalable web app deployment. Whether you're building a static or server-side rendered app, a mobile app landing page, or a web app, Amplify Hosting's fully managed Continuous Integration and Continuous Deployment (CI/CD) service has everything you need. You can quickly deploy web content with support for modern web frameworks like React, Angular, Vue, Next.js, Gatsby, Hugo, Jekyll, and more.
-
Amplify - 404 error when deploying Nextjs App
Details for anyone stumbling upon this : https://github.com/aws-amplify/amplify-hosting/issues/3398
-
Hosting site on Amplify with mp4/webm
After some diging found someone saying that i should edit `Rewrites and redirects` ( https://github.com/aws-amplify/amplify-hosting/issues/1416 )
-
How to Deploy a Next.js 13 Site with AWS Amplify
Head to AWS Amplify Hosting and click on the Host your web app button. You’ll be redirected to this page.
-
Can you host a React site with a database in AWS?
Just looked up the feature request and looks like they still don’t support it https://github.com/aws-amplify/amplify-hosting/issues/56
-
Building my blog with AWS Amplify and Next.JS
As of today, Amplify doesn't support Next.JS@12 fully and because of that, it'd be better and safer to downgrade to version 11 (of course we'd miss some of the awesome features from v12 but that's fine). So I'm making it "next": "11.1.4" in the package.json. Since we're downgrading it to v11, we need to downgrade usage of webpack from 5 to 4 and for doing that we need to add webpack5: false to our next.config.js file. I also add SVG support to that file for the future and it looks like this:
-
How does nextjs manage the SSR generated files?
After trying to deploy my company website on it, however, I'd recommend against using Amplify. It has issues with deploying & building as well as with server response times.
-
Bearcam Companion: Hosting with Amplify and GitHub
The Bearcam Companion application was pretty much ready to go after my last post on Lambdas. The final step (at least for a minimum viable product) was to publish the site. Not surprisingly, I chose to use AWS Amplify Hosting.
- Scalable AWS Infrastructure
sst
-
The 2024 Web Hosting Report
We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!
-
Hono v4.0.0
> But if you have a sufficiently large enough API surface, doing one lambda per endpoint comes with a lot of pain as well. Packaging and deploying all of those artifacts can be very time consuming, especially if you have a naive approach that does a full rebuild/redeploy every time the pipeline runs.
Yeah, thankfully SST [0] does the heavy lifting for me. I've tried most of the solutions out there and SST was where I was the happiest. Right now I do 1 functions per endpoint. I structure my code like url paths mostly, 1 stack per final folder, so that the "users" folder maps to "/users/*" and inside I have get/getAll/create/update/delete files that map to GET X/id, GET X, POST X, POST X/id, DELETE/id. It works out well, it's easy to reason about, and deploys (a sizable a backend) in about 10min on GitHub Actions (which I'm going to swap out probably for something faster).
I agree with the secrets/permissions aspect and I like that it's stupid-simple for me to attach secrets/permissions at a low level if I want.
I use NodeJS and startup isn't horrible and once it's up the requests as very quick. For my needs, an the nature of the software I'm writing, lambda makes a ton of sense (mostly never used, but when it's used it's used heavily and needs to scale up high).
[0] https://sst.dev
-
Lambda to S3: Better Reliability in High-Volume Scenarios
We will start by building a project with SST that provisions an API Gateway, a Lambda, and an S3 bucket. Once implemented, we'll look into testing for concurrent write conflicts or exceeding capacity limits.
-
How I saved 90% by switching NATs
I recently deployed a node websocket server using the SST Service construct. Until this point my stack had been functions and buckets. While I had no users 😢, I also had no costs 🤡.
-
Ask HN: What web development stack do you prefer in 2024?
Most my personal and side-business projects have very spiky load or just low load in general. Because of that I love using AWS Lambda as my backend since it scales to 0 and scales to whatever you have your limits set at.
I use SST [0] for my backend with NodeJS (TypeScript) and Vue (Quasar) for my frontend. For my database I use either Postgres or DynamoDB if the fit is right (Single Table Design is really neat). For Postgres I like Neon [1] though their recent pricing changes make it less appealing.
[0] https://sst.dev
[1] https://neon.tech
-
Meta's serverless platform processing trillions of function calls a day (2023)
Yup. Entire core business product for a succeeding startup, though it's a small team of contributors (<10), and a much smaller platform team. Serverless backend started in 2018. Been a blessing in many regards, but it has its warts (often related to how new this architecture is, and of course we've made our own mistakes along the way).
I really like the model of functions decoupled through events. Big fan of that. It's very flexible and iterative. Keep that as your focus and it's great. Be careful of duplicating config, look for ways to compose/reuse (duh, but definitely a lesson learnt) and same with CI, structure your project so it can use something off-the-shelf like serverless-compose. Definitely monorepo/monolith it, I'd be losing my mind with 100-150 repos/"microservices" with a team this size. If starting now I'd maybe look at SST framework[0] because redeploying every change during development gets old fast
I couldn't go back to any other way to be honest, for cloud-heavy backends at least. By far the most productive I've ever been
Definitely has its warts though, it's not all roses.
[0] http://sst.dev
-
Building a sophisticated CodePipeline with AWS CDK in a Monorepo Setup
Along the way, you find an excellent framework, SST. Which is much faster than CDK and provides a better DX1. Here is how you then define your MultiPipelineStack.
-
Create a Next.js Server Component S3 Picture Uploader with SST
SST is a powerful framework that simplifies the development of serverless applications. It offers a straightforward and opinionated approach to defining serverless apps using TypeScript. Built on top of AWS CDK, SST handles the complexity of setting up your serverless infrastructure automatically. SST is an open-source framework and is completely free to use.
- SST – modern full-stack applications on AWS
-
Do you believe AI will replace your job?
SST is an open-source framework designed to facilitate the development and deployment of Serverless stacks on AWS. It operates under the hood by integrating with Amazon CDK. However, its primary benefit is in allowing us to concentrate on creating resources using familiar languages like TypeScript, treating them as Infrastructure as Code (IaC).
What are some alternatives?
nextjs-wordpress-starter - A headless starter for WordPress powered by Next.js.
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
next-auth - Authentication for the Web.
vite - Next generation frontend tooling. It's fast!
commerce - Next.js Commerce
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
light-server - A lightweight cli static http server and it can watch files, execute commands and trigger livereload
esbuild - An extremely fast bundler for the web
nextjs-bootstrap-boilerplate - Boilerplate for a Next.js Project using Bootstrap Styling. Configured for TypeScript and Terraform.
docker-lambda - Docker images and test runners that replicate the live AWS Lambda environment
simple-otp - Simple OTP system with AWS Serverless
serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project