AWS User Group Singapore / Amazon Lex -- JAWSDAYS 2017
Download as PPTX, PDF2 likes659 views
The document discusses the AWS User Group in Singapore, highlighting its growth and activities since 2016, including a membership milestone of over 1000. It also introduces Amazon Lex, a service for building conversational interfaces using voice and text, detailing its features, use cases, and the structure of Lex bots for intent management. Additionally, it addresses developer challenges and provides an overview of how to implement and utilize the service for various applications, including event management.
![Response card
{
...,
responseCard: {
"version": 1,
"contentType":
"application/vnd.amazonaws.card.generic",
"genericAttachments": [
{
"title": "Flowers",
"subTitle": “Pick a flower”,
"imageUrl: "…",
"buttons": [
{"text": "tulips","value": "tulips"},
{"text": "lilies","value": "lilies"},
{"text": "roses","value": "roses"}
]
}
]
}
Pick a flower](https://image.slidesharecdn.com/slideshare-upload-170316013042/85/AWS-User-Group-Singapore-Amazon-Lex-JAWSDAYS-2017-37-320.jpg)
AWS User Group Singapore / Amazon Lex -- JAWSDAYS 2017
- 1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Alex Smith – Amazon Web Services Jo-Anne Tan – Gowild.sg JAWS DAYS 2017 Singapore AWS User Group Amazon Lex
- 3. AWS User Groups – ASEAN ASEAN 10 Member States • SG, TH, VN, ID, PH, MY, MM, KH, LA, BN https://aws.amazon.com/usergroups/
- 4. AWS User Groups – ASEAN Jakarta (Indonesia) Kuala Lumpur (Malaysia) Manila (Philippines) Singapore Bangkok (Thailand) Hanoi (Viet Nam) https://aws.amazon.com/usergroups/
- 5. AWS User Group - Singapore The “Little Red Dot” 5.75 Million • 3.9m Citizen/PR • 1.6m Other != China
- 6. AWS User Group - Singapore 4 Languages (-and more) Asia Pacific Hub “Kiasu”
- 9. Restarted regular meetings Passed 1000 members (2016-01-08)
- 10. Restarted regular meetings Passed 1000 members (2016-01-08) Changed to a better quality pizza shop
- 11. What worked well Regularity of meetings Good venue & AV Engineers.sg
- 12. Engineers.sg • Oct 2013 – PHP UG • >1200 videos • 40 Strong Team • More info: https://alexjs.co/engineers http://engineers.sg
- 13. What worked well Regularity of meetings Good venue & AV Engineers.sg
- 14. What worked well Regularity of meetings Good venue & AV Engineers.sg Beer
- 15. What didn’t work well AWS driven group Huge variance in talk quality Attendance/RSVP discrepancy
- 16. What’s next?
- 17. AWS User Group SG links: https://www.facebook.com/groups/awsugsg/ https://www.meetup.com/AWS-SG/ https://engineers.sg
- 18. What didn’t work well AWS driven group Huge variance in talk quality Attendance/RSVP discrepancy
- 19. Attendance vs RSVP Discrepancy User intent vs intended usage The trash can analogy Reduce the effort to comply
- 20. Amazon Lex
- 21. Why Did We Build Amazon Lex?
- 22. Advent of Conversational Interactions 1st Gen: Punch Cards & Memory Registers 2nd Gen: Pointers & Sliders 3nd Gen: Conversational Interfaces
- 25. Developer Challenges Speech Recognition Language Understanding Business Logic Disparate Systems Authentication Messaging platforms Scale Testing Security Availability Mobile Conversational interfaces need to combine a large number of sophisticated algorithms and technologies
- 26. Amazon Lex: New service for building conversational interfaces using voice and text
- 27. Amazon Lex - Features Text and Speech language understanding: Powered by the same technology as Alexa Enterprise SaaS Connectors: Connect to enterprise systems Deployment to chat services Designed for Builders: Efficient and intuitive tools to build conversations; scales automatically Versioning and alias support
- 28. Text and Speech Language Understanding Speech Recognition Natural Language Understanding Powered by the same Deep Learning technology as Alexa
- 29. Amazon Lex – Use Cases Informational Bots Chatbots for everyday consumer requests Application Bots Build powerful interfaces to mobile applications • News updates • Weather information • Game scores …. • Book tickets • Order food • Manage bank accounts …. Enterprise Productivity Bots Streamline enterprise work activities and improve efficiencies • Check sales numbers • Marketing performance • Inventory status …. Internet of Things (IoT) Bots Enable conversational interfaces for device interactions • Wearables • Appliances • Auto ….
- 30. Amazon Lex - Benefits High quality Text and Speech Language Understanding Built-in integration with the AWS platform Seamlessly deploy and scale Easy to use Cost effective
- 31. Lex Bot Structure Utterances Spoken or typed phrases that invoke your intent BookHotel Intents An Intent performs an action in response to natural language user input Slots Slots are input data required to fulfill the intent Fulfillment Fulfillment mechanism for your intent User input Response
- 32. Lex Bot Structure: Utterances Attend the user group Come to the meet up User inputs: I want to come to the next meetup Could I attend the next user group please Maps to RegisterUserForEvent intent RegisterUserForEvent intent UTTERANCES
- 33. Lex Bot Structure: Utterances Attend the user group on {eventDate} Come to the meet up on {eventDate} User inputs: I want to come to the next meetup on 12 March 2017 Could I attend the user group tomorrow please Maps to RegisterUserForEvent intent; eventDate=2017-12-03 RegisterUserForEvent intent UTTERANCES SLOTS eventDate AMAZON.DATE SLOT NAME SLOT TYPE
- 34. Lex Bot Structure: Fulfilment RegisterUserForEvent eventDate=2017-03-12 SLOT INTENT AWS Lambda Integration Intents and slots passed to AWS Lambda function for business logic implementation. Return to Client
- 35. Lambda input event { ..., "invocationSource": "FulfillmentCodeHook or DialogCodeHook", "userId": "user-id", "bot": {...}, "outputDialogMode": "Text or Voice”, "currentIntent": { "name": "intent-name", "slots": { "slot-name": "value", "slot-name": "value", "slot-name": "value" }, "confirmationStatus": "None, Confirmed, or Denied" } }
- 36. Lambda response object { ..., "dialogAction": { "type": "ElicitIntent, ElicitSlot, ConfirmIntent, Delegate, or Close", "fulfillmentState": "Fulfilled or Failed", "message": { "contentType": "PlainText or SSML", "content": "message to convey to the user" }, "intentName": "intent-name", "slots": { "slot-name": "value", "slot-name": "value", "slot-name": "value" }, "slotToElicit" : "slot-name", }
- 37. Response card { ..., responseCard: { "version": 1, "contentType": "application/vnd.amazonaws.card.generic", "genericAttachments": [ { "title": "Flowers", "subTitle": “Pick a flower”, "imageUrl: "…", "buttons": [ {"text": "tulips","value": "tulips"}, {"text": "lilies","value": "lilies"}, {"text": "roses","value": "roses"} ] } ] } Pick a flower
- 38. “Attend an Event” Attend event 12 March “Attend the event on 12 March” Automatic Speech Recognition Natural Language Understanding Intent/Slot Model Utterances “You are now confirmed for the next event on 12th March” Polly the on RegisterUserForEvent eventDate SLOT INTENT Validate eventDate slot value “You are now confirmed for the event on 12th March” Update DB
- 39. “Attend an Event” Attend event 12 March “Attend the event on 12 March” Automatic Speech Recognition Natural Language Understanding Intent/Slot Model Utterances “You are now confirmed for the next event on 12th March” Polly the on RegisterUserForEvent eventDate SLOT INTENT Validate eventDate slot value “You are now confirmed for the event on 12th March” Update DB
- 40. “Attend an Event” Attend event 12 March “Attend the event on 12 March” Automatic Speech Recognition Natural Language Understanding Intent/Slot Model Utterances “You are now confirmed for the next event on 12th March” Polly the on RegisterUserForEvent eventDate SLOT INTENT Validate eventDate slot value “You are now confirmed for the event on 12th March” Update DB
- 41. “Attend an Event” Attend event 12 March “Attend the event on 12 March” Automatic Speech Recognition Natural Language Understanding Intent/Slot Model Utterances “You are now confirmed for the next event on 12th March” Polly the on RegisterUserForEvent eventDate SLOT INTENT Validate eventDate slot value “You are now confirmed for the event on 12th March” Update DB
- 42. Event Manager Bot: Flow of Information GetUpcomingEvent INTENT GetUpcomingEventAgenda eventDate SLOT INTENT RegisterUserForEvent eventDate SLOT INTENTList summary of all events Show details for event on {eventDate} Register user for event on eventDate}
- 43. Event Manager Bot: Flow of Information GetUpcomingEvent INTENT GetUpcomingEventAgenda eventDate SLOT INTENT RegisterUserForEvent eventDate SLOT INTENT Do you want to hear more? YES NO “Okay. Bye!” ?