Support AWS Chatbot
e-moshaya opened this issue · comments
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
AWS Just Released Support for Chatbot in Cloudformation
Would be nice to gain this support in Terraform as well
New or Affected Resource(s)
N/A
Potential Terraform Configuration
resource "aws_chatbot_slack_channel_config" "slack" {
config_name = ""
iam_role_arn = ""
logging_level = ""
slack_channel_id = ""
slack_workspace_id = ""
sns_topic_arn = ""
}
References
@e-moshaya Thanks for this.
The AWS Chatbot service is currently in beta and there is not yet support in the AWS Go SDK.
@e-moshaya Thanks for this.
The AWS Chatbot service is currently in beta and there is not yet support in the AWS Go SDK.
This is now GA, but there is not yet support in the AWS Go SDK.
They don't have an API yet either, but they do offer cloudformation support.
I've started work on a public module which wraps Cloudformation to enable configuration of chatbot slack channels in terraform: https://github.com/waveaccounting/terraform-aws-chatbot-slack-configuration
I've published an alpha release (github) which has been tested to work, hoping to release an official 1.0 soon if anyone wants to use it!
@mwarkentin Maybe this can serve as inspiration: https://github.com/panos--/terraform-aws-chatbot-slack -- uses the CloudFormation workaround, too.
I've written this module and use it to receive AWS Health alerts and CloudWatch Alarms in Slack.
Hello, there's any update about this???
AWS Go SDK still does not have support for Chatbot. There is an open issue from Oct 7, 2020 requesting to add Chatbot support to the AWS Go SDK. We as a community could have been better about opening this issue ourselves back in March, but here we are. As soon as this issue is complete, this terraform-provider-aws issue can begin work.
I would suggest going over there and +1 to add visibility.
There is limited support for AWS Chatbot via Cloudformation.
This resource requires some setup to be done in the AWS Chatbot console. To provide the required Slack workspace ID, you must perform the initial authorization flow with Slack in the AWS Chatbot console, then copy and paste the workspace ID from the console.
Edit: Sorry just noticed there's a comment above that already mentions this. Apologies for the noise!
The creation of Slack channel configuration is available through Terraform's "AWS Cloud Control" (awscc) provider with this resource: awscc_chatbot_slack_channel_configuration
As you can see here: https://registry.terraform.io/providers/hashicorp/awscc/latest/docs/resources/chatbot_slack_channel_configuration
This configuration worked for me:
terraform {
required_providers {
awscc = {
source = "hashicorp/awscc"
version = "0.27.0"
}
}
}
provider "awscc" {
region = "us-east-1"
}
resource "awscc_chatbot_slack_channel_configuration" "test" {
configuration_name = "xxx"
iam_role_arn = "xxx"
slack_channel_id = "xxx"
slack_workspace_id = "xxx"
}
When will microsoft teams support be avialable for aws_cc provider? https://aws.amazon.com/blogs/aws/aws-chatbot-now-integrates-with-microsoft-teams/
That works but I think ideally it's supported in the main provider as well?
https://github.com/aws/aws-sdk-go-v2/releases/tag/release-2024-02-19
This release adds support for AWS Chatbot. You can now monitor, operate, and troubleshoot your AWS resources with interactive ChatOps using the AWS SDK.
Would love to see this ticket dispositioned again.. 816 votes and SDK is available.
I will start working on the Slack Channel Configuration resource.
FYI, Most used resources in the awscc provider:
- awscc_chatbot_slack_channel_configuration
- awscc_chatbot_microsoft_teams_channel_configuration
Looks like @madhavvishnubhatta is on the exact right path with #37222