By using AWS re:Post, you agree to the Terms of Use

Questions tagged with AWS Lambda

Sort by most recent
  • 1
  • 12 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Lexbot not eliciting all slot values in conversation

I'm trying to automate the process of creating a lexbot that receives slot values and processes them in a lambda function. The creation of the bot and functions are completed and fine, when I check the amazon lex console, the bot has been created, the intents are correct and the slot elicitations are there. However, when I run the bot and type an utterance, the bot goes straight to fulfilment lambda function as opposed to asking for the other slot values. All the slots have the slot constraint 'required', I'm just not sure why they are not being elicited by the bot. I will attach the json response from list_slots below: ![json response of list slots](/media/postImages/original/IMzBaosX9_QYWsel9MzYy8tQ) Below I will attach images of the bot specifications from the console. ![slot values](/media/postImages/original/IM4GGdRJpRQgqML7zXFSxlCA) ![shows the lambda function is called on fulfillment](/media/postImages/original/IMdjLiIZ32TqyaBpVplSnN8Q) ![Example of test output](/media/postImages/original/IM6u9Bp-ruQ22K-CXsN43bzA) I will also attach the content of the boto3 request I used to create the the slot in the first place. ![Example of the boto3 request used to create the slot](/media/postImages/original/IMauJP2jvYRu6dPSBpUkKxEA) The following is an image of my intent, to show that the fulfilment code hook is enabled: ![Code that shows the creation of the intent](/media/postImages/original/IMkSN5QrZaSymUBAX29f0R7w) My question is, why is the bot not asking for the other slot values when all the configuration suggests it should do otherwise?
0
answers
0
votes
4
views
asked 2 hours ago

Amplify auto-generated lambda functions using Node 12

I created an Amplify app with back-end a couple of weeks ago. This caused a few Lambda functions to be generated, such as "amplify-login-verify-auth-challenge-SHORTCODE" as described [here](https://docs.amplify.aws/console/adminui/access-management/). The functions use Node 12 as the runtime environment. Yesterday I received an email from AWS saying Node 12 will no longer be supported by AWS. Will Amplify be updated - or is there something I can do to make sure the Amplify-generated functions use a newer version of Node going forward? For reference, here is the content of the email: ``` Amazon Web Services, Inc. <no-reply-aws@amazon.com> Sun, Aug 14, 9:55 AM (1 day ago) to XXX Hello, We are contacting you as we have identified that your AWS Account currently has one or more Lambda functions using Node.js 12 runtime. We are ending support for Node.js 12 in AWS Lambda. This follows Node.js 12 End-Of-Life (EOL) reached on April 30, 2022 [1]. As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting November 14, 2022, Lambda will no longer apply security patches and other updates to the Node.js 12 runtime used by Lambda functions, and functions using Node.js 12 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Node.js 12 runtime. Starting December 14, 2022, you will no longer be able to update existing functions using the Node.js 12 runtime. We recommend that you upgrade your existing Node.js 12 functions to Node.js 16 before November 14, 2022. End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team. The following command shows how to use the AWS CLI [3] to list all functions in a specific region using Node.js 12. To find all such functions in your account, repeat this command for each region: aws lambda list-functions --function-version ALL --region us-east-1 --output text --query "Functions[?Runtime=='nodejs12.x'].FunctionArn" If you have any concerns or require further assistance, please contact AWS Support [4]. [1] https://nodejs.org/en/blog/release/v12.22.12/ [2] https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html [3] https://aws.amazon.com/cli/ [4] https://aws.amazon.com/support Sincerely, Amazon Web Services Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210 ```
1
answers
0
votes
11
views
asked 3 days ago
  • 1
  • 12 / page