Create Slack Channels

In this section, you are going to create Slack channels for centralizing notifications from AWS CodeDeploy and GitHub Actions workflow.

The Slack setup in the workshop does not fully align with Slack’s best practices. For more details, please refer to the Slack Docs.

Let’s start by creating a Slack workspace that represents your company or team.

1. Go to Slack get started page. Sign in with Google or another method of your choice.

0001

2. After successfully logging in, you might be asked to create a workspace. Click Create a Workspace.

0002

3. At step 1 of 5,

  • For What’s the name of your company or team?, enter fcj.
  • Click Next.

0003

4. At step 2 of 5,

  • For What’s your name?, enter fcj-member.
  • Click Next.

0004

5. At step 3 of 5, click Skip this step.

0005

Click Skip Step.

0006

6. At step 4 of 5,

  • For What’s your team working on right now?, enter devops on aws.
  • Click Next.

0007

7. At step 5 of 5, choose Start with Free.

0008

8. In the sidebar,

  • Click Add channels.
  • Choose Create a new channel.

0009

9. Enter Name as aws-codedeploy and then click Next.

00010

10. Select Private — only specific people option and then click Create.

Public channels are great for sharing information that should be accessible to everyone in organization, while private channels are best for conversations that should be limited to specific people. If you only want those working on a particular project to have access, opt for a private channel.

00011

11. Click Skip for now.

00012

12. Do the same from step 8 to 11 to create the following private channels

  • gha-ci for CI notifications from GitHub Actions,
  • gha-merge-group for merge group notifications from GitHub Actions,
  • gha-release for release notifications from GitHub Actions, and
  • gha-rollback for rollback notifications from GitHub Actions

You finally got 5 private Slack channels created.

00013