Is there any way to set data type of the input(in chabox) in amazon lex to password datatype or any way to mask the password shared in the AWS lex Chatbot?
Amazon Lex is entirely separate from the user interface used to pass messages to Lex.
So any configuration dealing with the chatbox, will need to be done within your specific channel's chat display settings. And that will differ between channels (Facebook Messenger, SMS, Skype, etc.).
If you are using the Lex Test Chat, be aware that it has its own unique formatting, built entirely separate from Lex, so don't confuse those two. Lex only deals with receiving messages, parsing the language, and delivering appropriate responses. How the incoming messages and outgoing responses are displayed is entirely controlled by the channel.
Just to give you an example of how something like this can be done using Facebook Messenger.
You can use Facebook Webview to open an html form inside the facebook chat that uses the password input:
<input type="password"...>
Related
I'm using AWS Pinpoint service for sending SMS messages, and I would like to add some HTML coding (such as: URLs, bullets, really simple stuff).
I wasn't able to manage it. The HTML is shown in the device as plain text. Do you know if there is some kind of configuration for the SMS message for being treated as HTML ?
Thanks!
I am using AWS Chime JS SDK and would like to send a private message to a user. By message I mean to show a popup modal to an specific user.
I've been going through the documentation, but overall I have not found how to send messages to specific users.
https://aws.github.io/amazon-chime-sdk-js/modules/apioverview.html#9-send-and-receive-data-messages-optional
Is this possible under Chime?
The data channel within Chime would not allow for this if you wanted secure and private messages. Optionally, you could filter on the inbound message on each client so that it only popped for the person you wanted. However, the Chime SDK also has a Messaging SDK that can be used for a case like this:
https://aws.amazon.com/blogs/business-productivity/build-meeting-features-into-your-amazon-chime-sdk-messaging-application/
You can create private channels. They are also persistent and can be used for other data sharing use cases.
I am new to Amazon aws, Is lex chat bot support video eg MP4 , ?
Assume something like this:
Bot: would you like to watch the tutorial?
Human: Yes.
Bot: displays a video
A video can be alone or with response card .
Is this possible????
You can define a custom payload as a response from a Lex bot (using a Lambda function for the fulfillment), but you would also have to integrate the Lex bot into an application that could appropriately handle that response (display the video based on the response from the Lex fulfillment lambda).
The supported message formats are:
PlainText—The message contains plain UTF-8 text.
SSML—The message contains text formatted for voice output.
CustomPayload—The message contains a custom format that you have created for your client. You can define the payload to meet the needs of your application.
Composite—The message is a collection of messages, one from each message group. For more information about message groups, see Message Groups.
Moere info on Lex messaging and the CustomPayload here: https://docs.aws.amazon.com/lex/latest/dg/howitworks-manage-prompts.html
So the answer is that it is possible, but not a built in functionality.
Amazon lex will be able to send whatever response is required, it's the job of chat client to render that response and displays accordingly.
There will be a different way to send a video in response to facebook messenger than slack or any other chat client.
If you need to deploy it to your website, you can check this and this out. It supports HTML and markdown components in response so you can send a video.
I had configured my chatbot using AWS Lex Chatbot service. My main intention to create chatbot is to integrate it to Facebook and the user's communication should possible in both text and voice. I integrated my chatbot to facebook successfully by following steps give in AWS documentation. BUt voice piece was not working on facebook. Please, provide me any suggestions or any reference blogs of integrating lex voice piece to Facebook along with the text.
Facebook Messenger doesn't interpret lex responses into Voice responses, at least not yet.
The event object received, when accessing Lex from Facebook, will generate requestAttributes and those specify the accepted content types under x-amz-lex:accept-content-types.
"requestAttributes": {
"x-amz-lex:accept-content-types": "PlainText"
},
As you can see, PlainText is the only accepted content-type. Even though Lex has 4 supported message content-types: 'PlainText', 'SSML', 'CustomPayload', and 'Composite'. See here.
From Facebook Messenger Docs:
The Messenger Platform allows you to attach assets to messages, including audio, video, images, and files.
Even though Facebook accepts attachments of audio, Lex only sends PlainText or SSML.
Lex does use Facebook's messsage attachments when it sends Response Cards, but the Response Cards can only have a Generic Type, so that it only sends images, not audio files. See here.
How can I accomplish to send email in Amazon SES with a custom email from for several domains.
For example, I have an application that is used by several clients, and we have a module to send emails. When we send an email it goes with the "amazonses.com domain", but what I want to accomplish is a custom from email for each client, each one has a different domain.
The process for doing this is entirely specific to the current SES configuration steps so its better I provide a link thats regularly updated.
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/mail-from-set.html
The short summary is that you can do this by choosing a FROM option for the emails you are sending from.
Programmatically Setting From
The link above points how how to use the API to programmatically change the FROM value. The link below is directly to the API call for setting from but to accomplish it you'd still need to follow the manual tutorial then replace its steps with equivalent API Calls.
http://docs.aws.amazon.com/ses/latest/APIReference/API_SetIdentityMailFromDomain.html