📢 Update

In v0.41.0, we added the

sst.Script

construct. You can use this script to do things like seeding the database, etc. A couple of things to note: • The script is not run on ur local machine or on the build server, it’s run inside a Lambda function; • The script uses your the Lambda function’s IAM credentials, not your local credentials; • The script can run for a maximum of 15 minutes; • The script is run on every deployment; • Live Lambda Dev is not enabled for scripts;

new Script(this, "Script", {
  function: "src/script.main",
  params: {
    hello: "world",
    tableName: table.tableName,
  },
});

Here are some more examples.

This is awesome, been looking to do exactly this over the last couple of days. I was looking at using a custom resources in cloudformation. Is that what is being used for this behind the scenes?

@George Evans Yup! You bet!

Awesome! For running post deploy database migrations mainly 👍

Ah gotcha! Keep me posted on ur experience!

oh wow

Thanks @Blake E! Could you share an example of what you are doing inside the scirpt? Just curious 😁

when I finish

Ah gotcha!

@Frank this is fantastic. I noticed that the deployment process outputs to the console when the Lambda/Script fails, but is silent when it succeeds. I was wondering if it would make sense to output any responses that the Lambda/Script returns? For example for a database initializer script, I’m returning the list of databases, which could be used to confirm that in fact the new database was created.

return {
          'statusCode': 200,
          'headers': {'Content-Type': 'application/json'},
          'body': json.dumps({**databases})
       }