sst

🐛 Bug Fix

• #1508 Fix: do not use dynamic file migrator in production (@thdxr)

Update using:

$ npx sst update 0.68.1
$ yarn sst update 0.68.1

🚀 Enhancement

• #1500 Update CDK to 2.15.0 (@fwang)

🐛 Bug Fix

• #1498 Console: fix KinesisStream consumers not showing in functions tab (@Manitej66)

📝 Documentation

• #1476 Add example for Angular (@Manitej66)

Update using:

$ npx sst update 0.68.0
$ yarn sst update 0.68.0

🚀 Enhancement

• #1483 Better packaging for @serverless-stack/node (@thdxr)
• #1459 Console: copy signed url of object instead of s3 url (@Manitej66)

🐛 Bug Fix

• #1470 Console: fix undefined error stack trace crash (@fwang)

📝 Documentation

• #1460 Console: fix dynamoDB copy (@Manitej66)

🆕 SST Console / API

This update features a new API Explorer that lets you to make HTTP requests to your sst.Api and sst.ApiGatewayV1Api. Easily set headers, query params and body to make a request against any of your routes and view the function logs as well as the response.

🚀 Enhancement

• #1451 Explorer: API (@thdxr)
• #1454 fixed showing the loading sign while creating new folder (@Manitej66)
• #1444 Clean up dependencies (@thdxr)

📝 Documentation

• #1442 Fix lambda transpiling issue in mongodb example (@Manitej66)

Update using:

$ npx sst update 0.67.0
$ yarn sst update 0.67.0

🐛 Bug Fix

• #1449 Function: do not set esbuild "external" without "bundle" is disabled (@fwang)

Update using:

$ npx sst update 0.66.3
$ yarn sst update 0.66.3

🚀 Enhancement

• #1448 sst start: add Lambda contexts required by Lambda power tool logger (@fwang)

🐛 Bug Fix

• #1439 sst start: need to hit ctrl-c twice to exit the process (@danieloi)

📝 Documentation

• #1435 Typo in auth.md (@julbrs)

Contributors

• Julien Bras (@julbrs)
• Mayowa Daniel (@danieloi)

Update using:

$ npx sst update 0.66.2
$ yarn sst update 0.66.2

🐛 Bug Fix

• #1443 sst start: setting NODE_OPTIONS in Lambda environment causes VSCode breakpoint not working (@fwang)
• #1441 sst start: fix large payload IllegalLocationConstraintException error in new regions (@fwang)

Update using:

$ npx sst update 0.66.1
$ yarn sst update 0.66.1

🆕 SST Console / DynamoDB

This update features a new DynamoDB Explorer that lets you query your sst.Table directly from the web console. You can scan the table, query specific keys and create/edit items.

🚀 Enhancement

• #1418 Explorer: Dynamo Console (@thdxr)
• #1413 Allow overriding s3 bucket and function props in debug stack (@fwang)
• #1431 sst start: show descriptive error message when remote Lambda timed out (@fwang)
• #1430 sst start: show descriptive message for "Unable to find function" (@fwang)
• #1412 Auth: import existing UserPool (@fwang)

🐛 Bug Fix

• #1420 RDS: fixed 0 showing as (@Manitej66)
• #1415 sst start: add trace to Python bootstrap.py error reporting (@estyrke)

📝 Documentation

• #1433 Fixed typo in docs (@ackinc)
• #1419 Update schema compiling for middy example (@Manitej66)

Committers:

• Anirudh Nimmagadda (@ackinc)
• Emil Styrke (@estyrke)

🐛 Bug Fix

• #1414 Copy migration to temp file to bust cache (@thdxr)
• #1411 Check for instanceof DebugStack is not reliable inside DebugApp (@fwang)

📝 Documentation

• #1406 Editing docs for the debug stack (@jayair)

Update using:

$ npx sst update 0.65.6
$ yarn sst update 0.65.6

🐛 Bug Fix

• #1401 RDS: Fix running migrations on windows (@thdxr)
• #1396 Prevent loading jsdom, which mocks fetch/XHR (@hermanbanken)

Committers:

• Herman (@hermanbanken)

Update using:

$ npx sst update 0.65.5
$ yarn sst update 0.65.5

🚀 Enhancement

• #1355 Add AAAA records to support IPv6 for APIs and static sites (@pupeno)

🐛 Bug Fix

• #1389 RDS: fix attachPermission does not grant secretsmanager:GetSecretValue (@fwang)

📝 Documentation

• #1375 Update README instructions for typescript-monorepo example (@abirtley)

Contributors

• Pablo Fernández (@pupeno)
• @abirtley

Update using:

$ npx sst update 0.65.4
$ yarn sst update 0.65.4

Major changes to customizing DebugStack

When you run sst start, SST deploys a debug stack to setup Live Lambda Development environment. Prior to this release, you only could customize the debug stack after the stack had been created using the debugStack() callback. Starting with this release, you have full control over the DebugStack.

What do I need to do

1. Rename the callback from debugStack(app, stack, props) to debugApp(app);
2. Create DebugStack inside the debugApp callback;

  new sst.DebugStack(app, "debug-stack");

3. If you used to reference props.stage, change it to app.stage

Examples

If you were adding a custom tag like this:

export function debugStack(app, stack, props) {
  cdk.Tags.of(app).add("my-stage", props.stage);
}

Change it to:

export function debugApp(app) {
  new sst.DebugStack(app, "debug-stack");
  cdk.Tags.of(app).add("test", `${app.stage}-${app.region}`);
}

You can also customize the stack name and the synthesizer.

export function debugApp(app) {
  new sst.DebugStack(app, "debug-stack", {
    stackName: app.logicalPrefixedName("live-debug"),
    synthesizer: new cdk.DefaultStackSynthesizer({
      qualifier: 'randchars1234',
    }),
  });

  cdk.Tags.of(app).add("test", `${app.stage}-${app.region}`);
}

Read more about customizing the DebugStack.

🚀 Enhancement

• #1387 Allow customizing the debug stack (@fwang)

🐛 Bug Fix

• #1388 ApiGatewayV1Api: cannot set restApiName (@fwang)

Update using:

$ npx sst update 0.65.3
$ yarn sst update 0.65.3

🚀 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