Slackbot Migration

In January of 2020, we upgraded the Slackbot to support deeper integrations into the core GorillaStack platform. This documentation details how users of the legacy Slackbot can port existing configuration data into the GorillaStack Real Time Events solution.

No changes have to be made to the Slack App installed in your workspace. It is now just pointing at a newer and improved API.

Overview

There are 3 steps to get started:

1. Register with GorillaStack
2. Link your Slack App to the GorillaStack platform with the command /gs link
3. Link your AWS Accounts to the GorillaStack platform

That's it! You can start with basic use cases covered in Templates.

If you would like to copy all of your existing track configurations from the legacy Slackbot, please send a message of /gs migrate-tracked-events in your Slack workspace. The new Slack app will respond to this command by mapping all your map track configurations to Rules.

Finally, you should delete unnecessary CloudFormation stacks that were deployed for the legacy Slackbot.

In more detail

1. Register with GorillaStack

Go to our web application registration page.

When registering, select the Real Time Events product.

For detailed, step-by-step information on this process, please see our user guide pages on registration, verifying your email address and creating your GorillaStack Team.

2. Link the Slack App to the GorillaStack platform

This links your user identity within your Slack workspace to your GorillaStack user account, allowing you to interact with GorillaStack within Slack.

The owner of each verified GorillaStack user account should send a message of /gs link into your Slack workspace.

You won't need to change the Slack App installation you have in place today. If you don't have the Slackbot installed yet (or have removed it) please install it here.

3. Link AWS Accounts to the GorillaStack platform

You will now need to connect AWS Accounts to the GorillaStack platform to start consuming CloudTrail data.

For detailed, step-by-step information on this process, please see our user guide page on Linking AWS Accounts.

4. (Optional) Copy your existing event tracking config from the legacy Slackbot to the GorillaStack platform

This step is optional, as you may wish to start with a fresh set of configurations from your Templates page, or by creating Rules manually.

To kick off the migration process, send a message of /gs migrate-tracked-events to your Slack workspace (you will need create privileges on rules within GorillaStack to do so).

Delete Legacy CloudFormation Stacks

You should now remove the GorillaStack-CloudTrail-Listener stack for each of the accounts that you linked to the legacy Slackbot. This stack is no longer required.

Feel free to use this script to search for these stacks via the AWS CLI.

#!/bin/bash

region_function () {
  region=$1
  if aws cloudformation describe-stacks --region $region --stack-name GorillaStack-CloudTrail-Listener 2>/dev/null 1>/dev/null;
  then
    aws cloudformation delete-stack --region $region --stack-name GorillaStack-CloudTrail-Listener
    aws cloudformation describe-stacks --region $region --stack-name GorillaStack-CloudTrail-Listener 2>/dev/null
  fi
}

regions=( $(aws ec2 describe-regions --query "Regions[].RegionName" --output text) )
for region in "${regions[@]}"
do
  region_function $region &
done

wait