feat: Email and slack integration integration cloud formation for bud… #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
YutongLi291
reviewed
Oct 30, 2024
|
|
||
| ## Introduction | ||
| AWS Deadline Cloud sends events to customer's default event bus https://docs.aws.amazon.com/deadline-cloud/latest/userguide/monitoring-eventbridge.html | ||
| This directory holds sample templates customers can use to setup notifications basis events received from Deadline Cloud |
There was a problem hiding this comment.
Either works for me! Done
leongdl
reviewed
Oct 30, 2024
|
|
||
| ## Introduction | ||
| AWS Deadline Cloud sends events to customer's default event bus https://docs.aws.amazon.com/deadline-cloud/latest/userguide/monitoring-eventbridge.html | ||
| This directory holds sample templates customers can use to setup notifications basis events received from Deadline Cloud |
There was a problem hiding this comment.
"sample templates" -> "sample Cloud Formation Templates"
leongdl
reviewed
Oct 30, 2024
| through mechanisms like email or slack. | ||
|
|
||
| ## Setup Instructions | ||
| Each template will have its own instructions on how to set up integrations, but in general they follow the below scheme: |
There was a problem hiding this comment.
"Each template" -> "Each Cloud Formation Template"
-> Because many customers use Terraform and other tech too!
leongdl
reviewed
Oct 30, 2024
| a. In Slack, on the left navigation pane, choose Automations. | ||
| ###### Note: If you do not see Automations in the left navigation pane, choose More, then choose Automations. | ||
|
|
||
| b.If AWS Chatbot is not listed, choose the Browse Apps Directory button. |
|
The file structure for the CloudFormation templates looks good to me 👍 |
leongdl
previously approved these changes
Oct 31, 2024
…get notifications Signed-off-by: Sakshi <[email protected]>
benl-2023
approved these changes
Nov 21, 2024
leongdl
approved these changes
Nov 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the problem/requirement? (What/Why)
We've launched Event bridge events for budget thresholds for customers https://docs.aws.amazon.com/deadline-cloud/latest/userguide/budget-threshold-events.html. We need to create a cloudformation template for customers to run on their account to setup consuming these events & sending them as notifications.
What was the solution? (How)
Publishing a CloudFormation Template sample for sending notifications over email and on slack for BudgetThresholdReached events.
What is the impact of this change?
Customers can use this template directly to setup their accounts for getting events as notifications over email and/or slack.
How was this change tested?
Tested this on own account as a customer would. Created the stacks using the CloudFormation Template and was able to get the slack and email notifications over configured channels.
Was this change documented?
Yes Readme files have been updated as necessary
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.