I have a pretty straightforward stack definition to try out a WebSocket API but, when running

sst start

it deploys and starts up but then logs the message

Missing region in config

and aborts with

Process finished with exit code 130 (interrupted by signal 2: SIGINT)

The deploy command I’m using is

sst start --stage ross-dev --region eu-west-2

The stack itself looks like this:

import * as sst from '@serverless-stack/resources';

export default class WebSocketStack extends sst.Stack {

  private api: sst.WebSocketApi;
  private connectionsTable: sst.Table;

  constructor(scope: <http://sst.App|sst.App>, id: string, props?: sst.StackProps) {
    super(scope, id, props)

    this.connectionsTable = this.createConnectionsTable();
    this.api = this.createApi();
    this.api.attachPermissions([this.connectionsTable]);

    this.addOutputs({
      ApiEndpoint: this.api.url
    })
  }

  private createConnectionsTable(): sst.Table {
    return new sst.Table(this, 'connections-table', {
      fields: {
        PK: sst.TableFieldType.STRING,
        connectionId: sst.TableFieldType.STRING,
      },
      primaryIndex: {
        partitionKey: 'PK',
      }
    })
  }

  private createApi(): sst.WebSocketApi {
    return new sst.WebSocketApi(this, 'WebsocketApi', {
      accessLog: false,
      routes: {
        $connect: "src/main/handlers/wsHandlers.webSocketHandler",
        $disconnect: "src/main/handlers/wsHandlers.webSocketHandler",
        sendMessage: "src/main/handlers/wsHandlers.webSocketHandler",
      },
      defaultFunctionProps: {
        environment: {
          CONNECTIONS_TABLE: this.connectionsTable.tableName,
          REGION: this.region,
        },
      }
    })
  }
}

Any thoughts on what could be going on?

hm I think @Omi Chowdhury has this same issue, wasn't able to figure it out

😄 I’ll give that a go, cheers

@thdxr yeah very likely.. taking a quick look..

This happened to me as well, I ran aws configure again, entered my IAM credentials and then noticed that the next prompt for default region was blank (the first time I had done this for the tutorial it had defaulted to the us-east-1), so I entered us-east-1 and then json for the next prompt that was also blank, and everything worked great.

@Ross Coundon @Jared Utah just pushed out a fix in v0.69.5. You don’t need to set the

AWS_REGION

manually. Give it a try and let me know if it works for you.

Yes, that worked, thanks for the super fast turnaround, Frank.

Thank you!