AWS Lex

[jch254]

Hi there,

I couldn't find any issues or code relating to AWS Lex: http://docs.aws.amazon.com/lex/latest/dg/API_Reference.html. It'd be great to be able to define entire bots as code instead of configuration through the AWS console. E.g. https://nicholasjackson.io/2017/04/25/slack-bot-aws-lambda.

More info: http://docs.aws.amazon.com/lex/latest/dg/programming-model.html#programming-model-build-time-api

Cheers!

[nicholasjackson]

Hey @jch254 LEX is not currently one of the supported features in the AWS provider. I was thinking about adding the extension but for creating a Slackbot it would only be possible to partially create the resources as of the way the interaction flow bounces between slack and AWS during configuration.

Also at present, the Slack API does not support configuration of integrations it can only really be used for sending and reading messages, basic user interaction stuff. I did ask Slack if they planned to release an admin API and they said they would like to but have not committed to a date.

If we could add the full workflow then I would gladly add the LEX endpoints however for now event though it would be cool it is not possible.

Feel free to ping me if you need any help.

Kind regards,

Nic

[jmstone617]

I don't see why a lack of the ability to spin up supporting infrastructure outside of AWS (e.g. Slack) would preclude the need for including the Lex configuration in this provider. Lex comes with it roles, Lambda functions, and other AWS-specific pieces of infrastructure that someone may want to spin up. Personally, I could use this feature in the AWS provider and would happily contribute.

[jzbruno]

Hello all,

I am working on adding the Lex resources. Current progress is shown in the PR above. Right now I am working on bots and intents.

Jack