We are going to use Seed to automate our serverless deployments and manage our environments.

Start by signing up for a free account here.

Create new Seed account

Let’s Add your first app.

Add your first Seed app

Now to add your project, select GitHub as your git provider. You’ll be asked to give Seed permission to your GitHub account.

Select Git provider

Select the repo we’ve been using so far.

Next, Seed will automatically detect the sst.json config in your repo. Click Add Service.

SST app detected

Seed deploys to your AWS account on your behalf. You should create a separate IAM user with exact permissions that your project needs. You can read more about this here. But for now we’ll simply use the one we’ve used in this tutorial.

Run the following command.

$ cat ~/.aws/credentials

The output should look something like this.

aws_access_key_id = YOUR_IAM_ACCESS_KEY
aws_secret_access_key = YOUR_IAM_SECRET_KEY

Seed will also create a couple of stages (or environments) for you. By default, it’ll create a dev and a prod stage using the same AWS credentials. You can customize these but we’ll use the defaults.

Fill in the credentials and click Add a New App.

Add AWS IAM credentials

Your new app is created. You’ll notice a few things here. First, we have a service called notes. It’s picking up the name from our sst.json. You can choose to change this by clicking on the service and editing its name. You’ll also notice the two stages that have been created.

Our app can have multiple services within it. A service (roughly speaking) is a reference to a sst.json or serverless.yml file (for Serverless Framework). In our case we just have the one service.

Seed app homepage

Now before we proceed to deploying our app, we need to enable running unit tests as a part of our build process. You’ll recall that we had added a couple of tests back in the unit tests chapter. And we want to run those before we deploy our app.

To do this, hit the Settings link and click Enable Unit Tests.

Click Enable Unit Tests in Seed

Back in our pipeline, you’ll notice that our dev stage is hooked up to main. This means that any commits to main will trigger a build in dev. To keep things simple, we’ll want to deploy to prod when we push to main. We also need to add our secret environment variables.

Let’s do that next.