This page provides instructions for cleaning up the resources created during the preceding modules. To clean up the AWS account after this workshop, you will need to remove all resources that were created for you. Note that the order of operations is important.
Remove the serverless application and the CI/CD pipeline created for managing it.
✅ Step-by-step directions
-
In the Lambda Console go to the Applications page.
-
Select the radio button next to your application.
-
Choose Actions and then Delete.
-
A pop-up with links will appear. Note that you must do one extra operation between steps 2 and 3 to successfully complete the deletion! Continue to step 5 below for detailed instructions. Failure to clean up resources could result in charges to your AWS account.
-
Perform step 1: Delete the application stack. When you click the application stack link, the CloudFormation console will open in a new tab. Choose Delete and confirm. Note that the page will not automatically refresh. Click the refresh button in the Overview section to verify if the process is complete.
-
Perform step 2: Delete the S3 bucket. When you click the S3 console link, search for the bucket name, select the checkbox, choose Delete, and confirm.
-
Go back to the Applications in the Lambda Console and close the pop-up.
-
Click on your application name to open it.
-
Choose CloudFormationRole to open it in the IAM console.
-
Under Permissions policies, choose the X next to the SNSFullAccess, IAMFullAccess, and CloudWatchFullAccess policies to detach them. Confirm detachment in the pop-up message. Do not detach the WorkerCloudFormationRolePolicy policy.
-
Go back to the Applications page in the Lambda Console.
-
Select the radio button next to your application.
-
Choose Actions and then Delete.
-
Perform step 3: Delete the toolchain stack. When you click the toolchain stack link, the CloudFormation console will open. Choose Delete and confirm. Note that the page will not automatically refresh. Click the refresh button in the Overview section to verify if the process is complete.
-
After completing step 3, refresh the Applications page to confirm if the application has been deleted.
Remove the credentials used to access CodeCommit repositories, unless you will use them again in the future.
✅ Step-by-step directions
- Go to the IAM Console.
- Choose Users in the left menu.
- Find the user you created in the AWS CodeCommit credentials step.
- Select the checkbox next to the user name and choose Delete user.
- Confirm deletion in the pop-up form.
Remove the AWS Chatbot that you configured today and delete the role created with it.
✅ Step-by-step directions
-
Go to the AWS Chatbot console
-
Choose your Slack workspace in the Configured clients list.
-
Click the name of the Slack channel you configured for notifications. A Slack channel details page will open.
-
Under IAM role, click the role name.
-
IAM Console will open in a new tab. Choose Delete role and confirm.
-
Return to the AWS Chatbot console and go back to the Slack workspace page.
-
Select the radio button next to the Slack channel you used for Chatbot notifications and choose Delete channel. Note that this action does not delete the Slack channel itself - it only removes the AWS Chatbot configuration for the channel.
-
Confirm deletion in the pop-up message.
-
Choose Remove workspace configuration and confirm deletion in the pop-up form.
Remove the Slack application from your Slack account
✅ Step-by-step directions
- Go to the api.slack.com dashboard.
- Choose Your Apps.
- Choose the Slack app you've created.
- Scroll to the bottom of the page and choose Delete App. Confirm deletion.
This marks completion of the workshop.