sst

🚀 Enhancement

• #1224 sst-env: add support for SST app directory lookup (@Ivo-Evans)
• #1347 sst-env: remove unused and add missing dependencies (@fkjellberg)

📝 Documentation

• #1376 Update docs with GraphQL console (@jayair)

Contributors

• Fredrik Kjellberg (@fkjellberg)
• @Ivo-Evans

Update using:

$ npx sst update 0.65.2
$ yarn sst update 0.65.2

🆕 SST Console / GraphQL

This update features a new GraphQL Explorer that lets you query your GraphQLApi or AppSyncApi directly from the web console.

💥 Breaking Change to ApolloApi

The ApolloApi has been renamed to GraphQLApi in preparation for some larger GraphQL focused features. Simply changing your code to use sst.GraphQLApi is all you should need to do.

Update using:

$ npx sst update 0.65.1
$ yarn sst update 0.65.1

🆕 SST Console / RDS

This update features a brand new tab in the SST Console that is meant to be used with our new RDS Construct. You can use the query editor to execute queries to inspect your database or insert new data. You can also use the migrations panel to view all of your migrations and execute them.

Update using:

$ npx sst update 0.64.1
$ yarn sst update 0.64.1

Major changes to NextjsSite

The NextjsSite construct uses the @sls-next/lambda-at-edge package from the serverless-next.js project to build and package your Next.js app to a structure that can be deployed to Lambda@Edge and CloudFront.

Prior to this release, SST used to include the @sls-next/lambda-at-edge package as a dependency. It caused two problems:

1. You cannot use a different version of @sls-next/lambda-at-edge
2. @sls-next/lambda-at-edge is installed even if you are not using the NextjsSite construct

Starting with this release, you are responsible for installing @sls-next/lambda-at-edge as a dependency in your SST app to use the NextjsSite construct.

What do I need to do

npm install -s @sls-next/lambda-at-edge
// or
yarn add @sls-next/lambda-at-edge

That's it! This should be a seamless transition for most people without any code changes. However, if you are hardcoding the bucket name, you need to change the name because this release will replace the bucket, and CloudFormation cannot replace it with the same name. For example, change this:

new NextjsSite(this, "Site", {
  path: "path/to/src",
  s3Bucket: {
    bucketName: "my-bucket",
  },
});

to

new NextjsSite(this, "Site", {
  path: "path/to/src",
  s3Bucket: {
    bucketName: "my-new-bucket",
  },
});

Update using:

$ npx sst update 0.63.0
$ yarn sst update 0.63.0

🆕 SST Console / Cognito

This update features a brand new tab in the SST Console. It allows you to explore user pools in your app and create new users or delete existing users.

Update using:

$ npx sst update 0.62.0
$ yarn sst update 0.62.0

Major changes to StaticSite

We made some changes to the StaticSite, ReactStaticSite, and ViteStaticSite constructs to speed up the deployment time.

Prior to this release, on each deployment, the site is deployed to a new folder inside the S3 bucket, and the CloudFront distribution is updated to point to the new folder. This process can sometimes take more than 5 mins. On rare occasions, this process can also causes intermittent downtime for low traffic sites. Starting with this release, the site is deployed to the root of the S3 bucket. And each subsequent deployment overwrites the files of the previous deployment.

Who is affected

This should be a seamless transition for most people without any code changes. However, if you are hardcoding the bucket name, you need to change the name because this release will replace the bucket, and CloudFormation cannot replace it with the same name. For example, change this:

new StaticSite(this, "Site", {
  path: "path/to/src",
  s3Bucket: {
    bucketName: "my-bucket",
  },
});

to

new StaticSite(this, "Site", {
  path: "path/to/src",
  s3Bucket: {
    bucketName: "my-new-bucket",
  },
});

This affects the StaticSite, ReactStaticSite, and ViteStaticSite constructs.

🚀 Enhancement

• #1350 StaticSite: speed up deployment (@fwang)
• #1342 Auth Console (@thdxr)
• #1348 Auth: add custom email and sms sender triggers (@fwang)

Update using:

$ npx sst update 0.61.3
$ yarn sst update 0.61.3

🚀 Enhancement

• #1343 ViteStaticSite: generate types definition for JS projects (@fwang)
• #1339 Cli: support AWS credentials with assume role and MFA (@fwang)

Update using:

$ npx sst update 0.61.2
$ yarn sst update 0.61.2

🚀 Enhancement

• #1335 Api: access log retention takes RetentionDays format (@fwang)

🐛 Bug Fix

• #1336 Generate truly unique function local ids (@thdxr)
• #1340 Do not ignore entire stacks folder for function watcher (@thdxr)
• #1303 Add support for AWS GovCloud (@mendellerner)

Committers:

• Mendel Lerner (@mendellerner)

Update using:

$ npx sst update 0.61.1
$ yarn sst update 0.61.1

📣 New Console Command

This release has a new sst console command that can point the console at different environments outside of your local (sst start). This allows you to look at CloudWatch logs and manage your app in production.

Learn more about it here: https://docs.serverless-stack.com/packages/cli#console

npx sst console --stage=production

🚀 Enhancement

• #1322 Add console command + cloudwatch logs (@thdxr)
• #1326 Function: show helpful error message when esbuild plugin is not found (@fwang)
• #1324 Support GraphQL formatPayload callback (@thdxr)

Update using:

$ npx sst update 0.61.0
$ yarn sst update 0.61.0

🚀 Enhancement

• #1304 New layout for console (@thdxr)

🐛 Bug Fix

• #1319 Fix for esbuild native import issue when using ESM (@thdxr)

📝 Documentation

• #1320 Tweaking styles for docs site (@jayair)

Update using:

$ npx sst update 0.60.11
$ yarn sst update 0.60.11

🚀 Enhancement

• #1250 NextjsSite: make image regenerator customizable (@bshrram)
• #1317 Function: add support for Python 3.9 (@fwang)

🐛 Bug Fix

• #1316 Cli: fix build error when folder path contain spaces (@fwang)

Contributors

• Bshr Ramadan (@bshrram)

Update using:

$ npx sst update 0.60.9
$ yarn sst update 0.60.9

🚀 Enhancement

• #1311 Cli: hide exports from outputs created by CDK (@fwang)

  If this error seems familiar to you, we added automatic early detection for this issue.

   ❌  dev-stackA failed: Export dev-stackA:ExportsOutputRefTableArn30B25837ED330C0 cannot be deleted as it is in use by dev-stackB
  

  SST will temporarily add the exports that are still in use. Read more about how it works.

• #1310 Cli: detect exports still in use and temporarily add to template (@fwang)

• #1295 Add RDS construct (@fwang)

• #1288 Add ViteStaticSite construct (@fwang)

🐛 Bug Fix

• #1313 Cli: stage prompt causes cli to not quit cleanly (@fwang)

📝 Documentation

• #1166 Getting started guide (@fwang)

Update using:

$ npx sst update 0.60.8
$ yarn sst update 0.60.8

🚀 Enhancement

• #1286 GraphQLApi Construct (@thdxr)

🐛 Bug Fix

• #1308 Cli: fix stack changes not redeployed in sst start (@fwang)
• #1302 NextjsSite: fix placeholder lambda functions (@fwang)
• #1301 Cli: disable xray tracing for local invocation (@fwang)
• #1298 Set aws-cdk-lib as external when transpiling CDK code (@fwang)

📝 Documentation

• #1262 Update examples to v0.60.4 (@fwang)

Update using:

$ npx sst update 0.60.6
$ yarn sst update 0.60.6

🐛 Bug Fix

• #1284 Fixes issue on windows with runtime environment(@thdxr)
• #1275 Cli: fix cdk bootstrap version mismatch (@fwang)

📝 Documentation

• #1281 Update readme examples link (@aisflat439)

Update using:

$ npx sst update 0.60.4
$ yarn sst update 0.60.4

ESM Support

There is now a new option bundle.format which can be set to "esm" to generate esm builds. We strongly recommend this and will become the default behavior in the future. It allows for features like top level await which makes things like loading secrets on cold-start a lot smoother.

Some libraries you are using may be written in a way that does not work with ESM at all so you may not be able to use this. We encourage opening issues to push more projects to ship ESM - if they are unable to it's a sign to look for an alternative.

🚀 Enhancement

• #1274 Support ESM format (@thdxr)

🐛 Bug Fix

• #1272 Cli: fix stacks with custom stack name fail to deploy (@fwang)

Update using:

$ npx sst update 0.60.2
$ yarn sst update 0.60.2

🚀 Enhancement

• #1266 Permissions: support Kinesis Firehose Delivery Stream (@fwang)
• #1138 added external custom domain support to Api construct (@Manitej66)

Update using:

$ npx sst update 0.59.4
$ yarn sst update 0.59.4

🐛 Bug Fix

• #1263 Cli: fix accounts not automatically bootstrapped (@fwang)

Update using:

$ npx sst update 0.59.1
$ yarn sst update 0.59.1

💥 Breaking Change: Updating to CDK v2

We migrated to CDK v2. Here is how to update your apps.

Estimated time: 15 minutes

Prerequisites

• Update Node.js to v14 or later
• Update SST to v0.57.0 or later

Steps

1. Run npx sst update 0.59.1

2. Open up your package.json and update CDK dependencies to v2.

   1. If you have @aws-cdk/core as a dependency, rename it to aws-cdk-lib.
   2. If you have @aws-cdk/assert as a dependency, remove it from your package.json.
   3. If you have one or more @aws-cdk/aws-XXXX dependencies, and if they are on the experimental package list below, rename them to @aws-cdk/aws-XXXX-alpha. For example, rename @aws-cdk/api-gatewayv2 to @aws-cdk/api-gatewayv2-alpha.
   4. If you have one or more @aws-cdk/aws-XXXX dependencies, and if they are not on the experimental package list below, remove them from your package.json.

3. Update the import in your CDK code to use v2 dependencies.

   1. If you import @aws-cdk/core, rename import * as cdk from "@aws-cdk/core" to import * as cdk from "aws-cdk-lib".
   2. If you import @aws-cdk/assert, rename import * as assert from "@aws-cdk/assert" to import * as assert from "aws-cdk-lib/assertions". Read more about using assertions here.
   3. If you import @aws-cdk/aws-XXXX, and if they are on the experimental package list below, rename import * as XXXX from "@aws-cdk/aws-XXXX" to import * as XXXX from "@aws-cdk/aws-XXXX-alpha". For example, rename import * as apig from "@aws-cdk/aws-apigatewayv2" to import * as apig from "@aws-cdk/aws-apigatewayv2-alpha".
   4. If you have one or more @aws-cdk/aws-XXXX dependencies, and if they are not on the experimental package list below, rename import * as XXXX from "@aws-cdk/aws-XXXX" to import * as XXXX from "aws-cdk-lib/aws-XXXX". For example, rename import * as sns from "@aws-cdk/aws-sns" to import * as sns from "aws-cdk-lib/aws-sns".

4. Run npx sst update 0.59.1 one more time.

5. Run npx sst diff to review the changes. If you are updating from SST v0.57.0 or later, the only major change is how CDK v2 handles CloudFormation parameters, which mostly affects AWS::Lambda::Function resources' Code properties.

Read more about updating to AWS CDK v2 here

Experimental packages

@aws-cdk/aws-amplify
@aws-cdk/aws-apigatewayv2
@aws-cdk/aws-apigatewayv2-authorizers
@aws-cdk/aws-apigatewayv2-integrations
@aws-cdk/aws-apprunner
@aws-cdk/aws-appsync
@aws-cdk/aws-batch
@aws-cdk/aws-cloud9
@aws-cdk/aws-codestar
@aws-cdk/aws-glue
@aws-cdk/aws-iot-actions
@aws-cdk/aws-iot
@aws-cdk/aws-iotevents
@aws-cdk/aws-ivs
@aws-cdk/aws-kinesisanalytics-flink
@aws-cdk/aws-kinesisfirehose
@aws-cdk/aws-kinesisfirehose-destinations
@aws-cdk/aws-lambda-go
@aws-cdk/aws-lambda-python
@aws-cdk/aws-msk
@aws-cdk/aws-neptune
@aws-cdk/aws-redshift
@aws-cdk/aws-route53resolver
@aws-cdk/aws-servicecatalog
@aws-cdk/aws-servicecatalogappregistry
@aws-cdk/aws-synthetics

🚀 Enhancement

• #1245 CDK v2 (@fwang)

🐛 Bug Fix

• #1252 Do not do anything special for Go directory handlers (@thdxr)

In this release we are adding an anonymous telemetry collection program to SST. It's completely optional but it really helps us improve SST. You can read more about this over on our docs.

You can also check out how this is implemented in this PR: https://github.com/serverless-stack/serverless-stack/pull/1236. And the source for the service that stores these anonymous events is also open source: https://github.com/serverless-stack/telemetry

You can opt-out of this if you'd not like to share any information.

npx sst telemetry disable

If you have any questions or concerns, feel free to contact us.

🚀 Enhancement

• #1236 Cli: Add anonymous telemetry collection (@fwang)

📝 Documentation

• #1254 Fix a typo in anonymous-telemetry.md (@thgick)

Contributors

• Thomas Gick (@thgick)

Update using:

$ npx sst update 0.58.0
$ yarn sst update 0.58.0

🐛 Bug Fix

• #1248 Fix bundle disabling (@thdxr)

Update using:

$ npx sst update 0.57.4
$ yarn sst update 0.57.4