I believe that there's a typo in serverless-bot-framework/deployment/serverless-bot-framework.template, line 1308.

should be:
"SampleWebclientPackage": { "Fn::Join": [ "", ["https://s3.", { "Ref": "AWS::Region" }, ".amazonaws.com/", "%%BUCKET_NAME%%", "-", { "Ref": "AWS::Region" }, "/serverless-bot-framework/%%VERSION%%/sample-webclient.zip" ] ] },

instead of:
"SampleWebclientPackage": { "Fn::Join": [ "", ["https://s3-", { "Ref": "AWS::Region" }, ".amazonaws.com/", "%%BUCKET_NAME%%", "-", { "Ref": "AWS::Region" }, "/serverless-bot-framework/%%VERSION%%/sample-webclient.zip" ] ] },

Is your feature request related to a problem? Please describe.

No Japanese language supported.

Describe the feature you'd like

Japanese is now supported in Lex. So, I am very happy if the Serverless Bot Framework also supports it.

Additional context

Add any other context or screenshots about the feature request here.

I just followed the instructions given in "https://docs.aws.amazon.com/solutions/latest/serverless-bot-framework/deployment.html". When I try this in a chrome browser, the bot does not seem to respond and always it returns back with '...'. Could it be a Cognito access problem?

As specified on https://linux.die.net/man/1/sed , there isn't supposed to be a space between the -i option and its argument. The sed in msys2 complains

sed: can't read : No such file or directory

as it assumes anything that isn't prefixed by an option is a filename. Presumably the author's sed behaves differently, which is actually a fairly dangerous unix api bug, but is harmless here, since sed merely complains but doesn't do anything differently.

Hi,

README.md file says that second parameter to the build-s3-dist.sh is AWS region but inside script it is clear the deployment version.

A clear and concise description of what the bug is.

Details:

/home/ec2-user/environment/serverless-bot-framework/source/infrastructure/test/corelambda-construct.test.ts:13
import { SynthUtils } from '@aws-cdk/assert';
       ^

SyntaxError: Unexpected token {

  at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1350:14)

FAIL test/cognito-api-lambdas-construct.test.ts
● Test suite failed to run

Jest encountered an unexpected token

Steps to reproduce the behavior

1. Step One: clone repo into a fresh cloud9 environment
2. Step Two: run the tests shell script
3. [...]

Expected Result

A clear and concise description of what you expected to happen.
Exptected tests to pass

Actual Result

A description of what is the result and/or error messages you got when you faced this issue.
Test Suites: 10 failed, 10 passed, 20 total

Other information:

1. Version of the Solution (e.g., v1.1.0):

   To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0027) AWS Serverless Bot Framework v1.2.0 - This AWS CloudFormation template helps you provision the AWS Serverless Bot Framework stack without worrying about creating and configuring the underlying AWS infrastructure". If the description does not contain the version information, you can look at the mappings section of the template:

Mappings:
  Solution:
    Data:
      ID: SO0027
      Version: 'v1.2.0'

2. Region where CloudFormation template is deployed (e.g., us-east-1):
3. Did you make any change in the source code? If yes, what are the relevant changes (if publicly available)?:
4. Troubleshooting steps attempted:
5. Were there any errors in the Cloudwatch logs?:
6. Screenshots (please DO NOT include sensitive information):
7. Did you use the Sample Weather Service (please DO NOT include API KEY) ? Yes / No

Stack Parameters

Cloudformation Stack Parameters (please DO NOT include sensitive information like S3 bucket name, IP address, credentials, etc):

1. Bot Name:
2. Bot Language:
3. Bot Gender:

Additional context

Add any other context about the problem here.

Describe the issue

What is the difference between this project and QnAbot. Which is strategic and supported if you were to build on either?
https://github.com/aws-samples/aws-ai-qna-bot

I have executed the './build-s3-dist.sh bucket-base-name v1.0' command successfully and the Lambda package is also built successfully on my server. But I still don't know what I need to do next and how to use the Lambda package. Besides, after executing the command, there isn't anything in my bucket. Thanks.

Hi guys!

Managed to get the Serverless bot framework up and running, i will like to add in new lambda functions but keeps getting stuck executing commands to the new lambda functions

What i did so far:

1. i edited the knowledge.json file with new lambda function configurations
2. create a lambda function similar to the 2 other lambda (password reset + weather checks)

what are the missing steps i didn't cover?
Please help to enlightened me, thanks folks! Cheers

Regards,
ak86

This is not really an issue but it is an enquiry. Various places it is mentioned that it uses Lex. But, in the architecture diagram or checking the services the stack installed, Lex is no where seen. I do understand that the solution does Natural Language Processing (NLP). How is it doing NLP if Lex is not in use?