Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Security to Self-Hosted Communication Widgets #242

Open
pminumula opened this issue Oct 31, 2024 · 1 comment
Open

Add Security to Self-Hosted Communication Widgets #242

pminumula opened this issue Oct 31, 2024 · 1 comment

Comments

@pminumula
Copy link

The standard communication widget includes built-in security, but there’s no clear guidance for securing Option 3: Customized Widget and Chat Interface UI (Self-Hosted).

Is there documentation on encrypting and securing data between the self-hosted widget and the backend?
An API or settings to apply similar security protocols as in the standard widget.

@haomingli2020
Copy link
Collaborator

Hi @pminumula,

The Connect Hosted Comms Widget uses Json Web Token for security. Please refer to this doc for more details.
In general, you can build a backend service which can 1/ generate a JWT with a secret and 2/ validate a JWT against the secret. Then you can have your web application call this backend to generate and pass a JWT (with a short TTL) when starting a chat, and in your lambda function where you call the AmazonConnect StartChatContact API, you can validate the JWT before making the API call.
You can build other security layers like throttling within the API gateway layer. https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html

Please let me know if you have other questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants