sst

📣 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

🐛 Bug Fix

• #1244 Require build function for handler (@thdxr)

Update using:

$ npx sst update 0.57.2
$ yarn sst update 0.57.2

💥 Breaking Change in CDK

If you are using the Api, ApolloApi, or WebSocketApi construct in your app, and if you are configuring JWT or CUSTOM authorizers, there has been a recent change. And here is what you need to change after you update.

If you are using Api or ApolloApi with HttpJwtAuthorizer authorizer

Change this:

new HttpJwtAuthorizer({
  jwtAudience: ["UsGRQJJz5sDfPQDs6bhQ9Oc3hNISuVif"],
  jwtIssuer: "https://myorg.us.auth0.com",
})

to:

new HttpJwtAuthorizer("Authorizer", "https://myorg.us.auth0.com", {
  jwtAudience: ["UsGRQJJz5sDfPQDs6bhQ9Oc3hNISuVif"],
})

If you are using Api or ApolloApi with HttpUserPoolAuthorizer authorizer

Change this:

new HttpUserPoolAuthorizer({
  userPool,
  userPoolClients: [userPoolClient],
})

to:

new HttpUserPoolAuthorizer("Authorizer", userPool, {
  userPoolClients: [userPoolClient],
})

If you are using Api or ApolloApi with HttpLambdaAuthorizer authorizer

Change this:

new HttpLambdaAuthorizer({
  authorizerName: "LambdaAuthorizer",
  handler: new sst.Function(this, "Authorizer", {
    handler: "src/authorizer.main",
  }),
})

to:

const authorizer = new sst.Function(this, "AuthorizerFn", {
  handler: "src/authorizer.main",
});

new HttpLambdaAuthorizer("LambdaAuthorizer", authorizer, {
  authorizerName: "LambdaAuthorizer",
})

If you are using WebSocketApi with HttpLambdaAuthorizer authorizer

Change this:

new HttpLambdaAuthorizer({
  authorizerName: "LambdaAuthorizer",
  handler: new sst.Function(this, "Authorizer", {
    handler: "src/authorizer.main",
  }),
})

to:

const authorizer = new sst.Function(this, "AuthorizerFn", {
  handler: "src/authorizer.main",
});

new WebSocketLambdaAuthorizer("LambdaAuthorizer", authorizer, {
  authorizerName: "LambdaAuthorizer",
  identitySource: ["route.request.header.Authorization"],
})

More info

🚀 Enhancement

• #1242 Update CDK to v1.138.0 (@fwang)
• #1240 Console: Filter out stacks that do not match supported console version (@thdxr)
• #1217 Console: Leave the function request body after an invocation (@Manitej66)

🐛 Bug Fix

• #1238 Console: Page through all cloudformation stacks (@thdxr)
• #1215 Console: Show sign if bucket is empty (@Manitej66)
• #1235 Console: Limit how fast stack metadata is fetched (@thdxr)
• #1231 Console: Do not crop image in preview (@Manitej66)
• #1227 Console: Dark theme doesn't applied to splash (@Manitej66)
• #1214 Console: Initialize ws server after runtime server (@thdxr)

Contributors

• Mischa Spiegelmock (@revmischa)

Update using:

$ npx sst update 0.57.0
$ yarn sst update 0.57.0

🐛 Bug Fix

• #1219 Emit external source maps when bundling for prod (@thdxr)
• #1211 fix: invocation response ERROR src property must be a valid json object (@Manitej66)

Update using:

$ npx sst update 0.56.2
$ yarn sst update 0.56.2

🐛 Bug Fix

• #1209 Cli: sst start fails to start when custom stackName used (@fwang)

Update using:

$ npx sst update 0.56.1
$ yarn sst update 0.56.1

🆕 SST Console / S3

This update features a brand new tab in the SST Console. It allows you to explore the S3 buckets in your app. You can add and remove files and folders; browse and navigate them in real-time! And of course it comes in dark and light mode. A big thanks to @Manitej66 and @thdxr for their work on this.

📝 Documentation

• #1192 S3 Console (@thdxr)
• #1200 Display last update time on docs (@micalevisk)
• Cli: deploy skipped when stacks are in the ROLLBACK_COMPLETE state (@fwang)

Contributors

• Micael Levi L. Cavalcante (@micalevisk)

Update using:

$ npx sst update 0.56.0
$ yarn sst update 0.56.0

🐛 Bug Fix

• Fix issue with SSO credential loading process with console (@thdxr)

Update using:

$ npx sst update 0.55.1
$ yarn sst update 0.55.1

🆕 SST Console

Getting Started

1. Upgrade to v0.55.0
2. Run sst start
3. Head over to the Console link — SST Console: https://console.serverless-stack.com/my-app/dev/local
4. Enjoy!

Note that, the Console doesn't support Safari yet. It doesn't allow connecting to the localhost http endpoint. We'll be adding support for it in an upcoming release.

What's New

The SST Console is back and it's better than ever! Here's what's new.

1. It has a now has a new home — console.serverless-stack.com and it automatically connects to your local sst start.

2. There are 3 tabs in the Console:

   1. Local: This'll show you all your local function invocations grouped by request in real-time.
   2. Stacks: Here you can get a quick overview of all your stacks and their outputs and resources.
   3. Functions: This lists all the functions in your constructs and lets you invoke them.

3. There's also a really helpful Replay button for your invocations. It'll replay the specific Lambda invocation, allowing you to easily debug your functions!

And finally, it comes in both dark and light mode 🌝🌚

So give it a try and let us know what you'd like to see next!

🚀 Enhancement

• #1188 SST Console (@thdxr)

🐛 Bug Fix

• #1178 Fix reload functionBuilder (@thdxr)

📝 Documentation

• #1109 Update MongoDB example with serverless option (@Manitej66)

Update using:

$ npx sst update 0.55.0
$ yarn sst update 0.55.0

🚀 Enhancement

• #1172 Function: functionName takes callback (@fwang)

🐛 Bug Fix

• #1167 Fix esbuild treating warnings as errors (@thdxr)
• #1173 Bucket: allow multiple addNotifications calls within the same scope (@fwang)

📝 Documentation

• #1171 Fix a typo in CONTRIBUTING.md (@fishmandev)

Committers:

• Dmitriy Fishman (@fishmandev)

Update using:

$ npx sst update 0.54.4
$ yarn sst update 0.54.4