Then, review the Statement section of access policy. Choose the topic that you subscribed your AWS Chatbot to. In the left navigation pane, choose Topics.ģ. Make sure that your Amazon SNS topic's access policy grants the required permissions for another AWS service to publish messages to the topicĢ.
#Chatbot aws full
If you see an Event Received is not supported error message, then the service publishing messages to your topic isn't supported by AWS Chatbot.įor a full list of services that are supported by AWS Chatbot, see Using AWS Chatbot with other AWS services. Review your AWS Chatbot CloudWatch Logs for the following error message: Event Received is not supported. Make sure that the AWS service that's publishing messages to your Amazon SNS topic is supported by AWS Chatbot Make sure that you send Amazon SNS notifications to your AWS Chatbot only through one of the services that are supported by AWS Chatbot.
Make sure that you're not manually publishing messages to your Amazon SNS topicĪWS Chatbot doesn't support messages that are manually published to an Amazon SNS topic. Note: To test the setup, use your AWS Chatbot configuration to send a test notification. If the AWS Chatbot endpoint isn't listed as a topic subscription, then you must subscribe your Amazon SNS topic to your AWS Chatbot. Under Topic subscriptions, make sure that the following AWS Chatbot endpoint is listed. Then, choose the name of your Amazon SNS topic.ģ.
In the left navigation pane, choose Topics. Make sure that the AWS Chatbot endpoint is listed as a topic subscription for your Amazon SNS topicĢ. If the topic isn't listed, you must subscribe your Amazon SNS topic to your AWS Chatbot. In the Details pane, under Topics, verify that your Amazon SNS topic is listed. Choose your Slack channel in the Slack workspace configuration, or your webhook in the Amazon Chime webhooks list.ĥ. Under Configured clients, choose Slack or Amazon Chime based on your use case.ģ. Make sure that your AWS Chatbot is subscribed to your Amazon SNS topicĢ. (For Slack and Amazon Chime) Verify that the communication channel between the Amazon SNS topic and the AWS Chatbot is configured correctly To add the AWS Chatbot to a private Slack channel, run the /invite command in the private channel. If you see a channel_not_found error message, then your AWS Chatbot app hasn't been added to the private channel. Review your AWS Chatbot CloudWatch Logs for the following error message: channel_not_found. (For private Slack channels only) Make sure that the AWS Chatbot app is added to the Slack channel
#Chatbot aws install
To install the AWS Chatbot app on your Slack workspace, follow the instructions in Set up chat clients for AWS Chatbot. If you see an account_inactive error message, then your AWS Chatbot app isn't installed on your Slack workspace. Review your AWS Chatbot CloudWatch Logs for the following error message: account_inactive. Make sure that the AWS Chatbot app is installed on your Slack workspace If the subscribed Slack channel is deleted, you must create a new Slack channel and configure the new channel to receive notifications from your topic. Note: You can't undelete a Slack channel.
#Chatbot aws archive
To unarchive a channel, see Archive or delete a channel in the Slack help center. All the apps in archived or deleted Slack channels are deactivated. Make sure that the Slack channel isn't archived or deletedĪrchived or deleted Slack channels can't receive messages. (For Slack only) Verify that the communication channel between the AWS Chatbot and the Slack channel is configured correctly Resolution Turn on CloudWatch Logs for your AWS Chatbotįollow the instructions in Accessing Amazon CloudWatch Logs for AWS Chatbot. (For Slack and Amazon Chime) The communication channel between the Amazon SNS topic and the AWS Chatbot.(For Slack only) The communication channel between the AWS Chatbot and the Slack channel.If your Amazon SNS topic's notifications aren't reaching your AWS Chatbot, then one of the following is misconfigured:
0 kommentar(er)
