Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Terraform module for building and deploying Next.js apps to AWS. Supports SSR (Lambda), Static (S3) and API (Lambda) pages.
| Date | Stars |
|---|---|
| 2026-07-24 | 1477 |
| 2026-07-25 | 1477 |
| 2026-07-28 | 1477 |
| 2026-07-30 | 1477 |
| 2026-08-06 | 1477 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
<blockquote>
<p align="center">
<strong>Note</strong>
<br />
The main branch currently contains the atomic deployments alpha preview.
<br />
For the lastest stable release, check out the <a href="https://github.com/milliHQ/terraform-aws-next-js/tree/v0.x"><code>v0.x</code> branch</a>.
</p>
<p align="center">
Please see our blog post <a href="https://milli.is/blog/the-road-to-atomic-deployments" target="_blank" rel="noopener">"The road to Atomic Deployments"</a><br />or watch the latest release review for more information:
<br />
<br />
<a aria-label="Terraform Next.js for AWS: First look at the new atomic deployments feature" href="https://www.youtube.com/watch?v=NY3zKnIcLd4" target="_blank" rel="noopener">
<img src="https://img.youtube.com/vi/NY3zKnIcLd4/0.jpg" height="260px">
</a>
</p>
</blockquote>
---
# Terraform Next.js module for AWS
A zero-config Terraform module for self-hosting Next.js sites serverless on AWS Lambda.
## Features
Some features are still under development, here is a list of features that are currently supported and what we plan to bring with the next releases:
- ✅ Supports any version of [Next.js](https://nextjs.org/)
- ✅ [Terraform](https://www.terraform.io/) `v0.15+`
- ✅ Unlimited parallel deployments of Next.js apps (atomic deployments)
- ✅ Static, SSG, Lambda and API pages (with [dynamic routes](https://nextjs.org/docs/routing/dynamic-routes))
- ✅ Automatic expiration of old static assets
- ✅ [Rewrites](https://nextjs.org/docs/api-reference/next.config.js/rewrites) & [Redirects](https://nextjs.org/docs/api-reference/next.config.js/redirects)
- ✅ [Image Component & Image Optimization](https://nextjs.org/docs/basic-features/image-optimization) support
- 🚧 [Incremental Static Regeneration](https://nextjs.org/docs/basic-features/data-fetching#incremental-static-regeneration)
- ⛔️ [Middleware](https://nextjs.org/docs/advanced-features/middleware) (Not supported by Lambda@Edge / CloudFront functions)
## Architecture
The Next.js Terraform module is designed as a full stack AWS app. It relies on multiple AWS services and connects them to work as a single application:
## Usage
### Prerequisites
You should have the following tools installed:
- [Terraform](https://www.terraform.io/downloads)
- [Node.js](https://nodejs.org)
- [Bash](https://www.gnu.org/software/bash/) & [curl](https://curl.se/) (Should be available by default on many Linux based images or macOS)
> **Note:** Additionally we assume here that you already have a public [Route53 Hosted Zone](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/AboutHZWorkingWith.html) associated with your AWS account.
>
> This is a requirement in the preview phase of atomic deployments, where each deployment gets a unique subdomain assigned.
> It will change once atomic deployments become generally available.
### Setup the Next.js Terraform module
The Terraform module contains the system that is later used for creating new deployments and managing the aliases (domains) for your Next.js app(s).
Creating the Terraform stack is only required on initial setup and creates the global resources (CloudFront distributions, DynamoDB tables, S3 storage) that is used for handling incoming requests to your website.
Create a new `main.tf` file in an empty folder (or add it to your existing Terraform stack) and add the following content:
```tf
terraform {
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 4.0"
}
}
}
# Main region where the resources should be created in
# Should be close to the location of your viewers
provider "aws" {
region = "us-west-2"
}
# Provider used for creating the LExcerpt of 17,918 characters
Read on GitHub
364
JJ Kasper · @Vercel · United States
206
Steven · @vercel
105
42
Andy
33
32
Nathan Rajlich · @vercel · United States
25
12
9
6
5
5
4
3
Tim Neutkens · Vercel · Netherlands
3
3
2
2
2
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:467f6e41a0d15d47, topic:serverless