sitedoc.blogg.se - Aws chatbot terraform

#Aws chatbot terraform how to
#Aws chatbot terraform install
#Aws chatbot terraform archive
#Aws chatbot terraform code

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

#Aws chatbot terraform 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.

#Aws chatbot terraform 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.

#Aws chatbot terraform code

The commented Lambda code in index.js has the code to return the reponses with buttons to be rendered by Lex V2.ĪWS console gives an option to migrate a V1 bot to v2 bot.If your Amazon SNS topic's notifications aren't reaching your AWS Chatbot, then one of the following is misconfigured: Amplify doesn't support connecting to V2 Lex at the time of writing this POC.

#Aws chatbot terraform how to

The commented code in main.ts shows the way on how to connect to a V2 bot using a third party plugin. At the time of creating this POC, terraform supports creating a bot in V1 only. This is where you provide your chatbot name as created on Lex.ĪWS Lex V2 offers more features than V1. for chatbot directive, refer this link of documentation.

Setup Cognito and lex chatbot directives in files mentioned in above section.

Run the amplify setup commands from above url inside the my-chatbot-app folder.

Follow Amplify docs ( ) and select angular.

Auth component will have cognito auth, and home component will have chat component.

Create Auth and Home controller using ng g c command.

npm install -g ng new my-chatbot-app -routing -styles=scss.

Mark room type slot as not required, and let the if condition in lambda to check for the slot value, and render the response cards buttons using the json as returned from the Lambda.

index.js - Lambda code with branching logic.

- Amplify provided directive for Lex chatbot.

- Amplify provided directive for cognito login page.

- Import and configure AmplifyAngularModule and AmplifyService.

maint.ts - Configure Amplify using the export file mentioned above.

aws-exports.js - not committed, has all details about cognito pool created by Amplify.

If you gave IAM role for authenticated user only in step 4, then first login using cognito, then open localhost:4200/home to access the chatbot.

ng serve or amplify serve, then open localhost:4200.

Give either/both the roles policies for Lex.

Go to the user pool -> click federated identities -> click on the identity -> click edit identity pools -> get the IAM roles for authenticated and un-authenticated users.

Amplify push to set up Cognito user pool.

Visit the terrafrom folder, and follow the Readme to setup AWS Lex chatbot.

Our Amplify based angular app has cognito to authenticate the user,Īnd the user with correct IAM permissions granted, will be able to connect to AWS Lex chatbot. Create a AWS Lex chatbot using Terraform, and access it via angular app.Īmplify makes it very easy to integrate yout angular code with Lex chatbot.