Skip to main content
Deploy the CloudFormation stack so your Amazon Lex V2 conversation events stream from CloudWatch into Operata — a test contact that routes through your Lex bot shows the bot’s intents, slots, and fulfillment data in the Operata console within five minutes of contact end.

​
Before you start

Configure conversation logging per bot alias in the Amazon Lex V2 console. Operata consumes the text-based log stream.

​
Steps

​
1. Send Operata the install details

Contact Operata Support with:
  • AWS region hosting your Lex bots.
  • CloudWatch log group name for the Lex conversation logs — usually /aws/lex/<log-group-name>. To find it for a specific bot, open the Amazon Lex console, select the bot, open Deployment → Aliases, and copy the CloudWatch Log Group Name value from the right-hand panel.
  • Operata Group ID — Operata can confirm yours if you do not have it on hand.
Operata returns a quick-create CloudFormation link pre-filled with your configuration. Click the link to open the CloudFormation console. Every parameter is pre-populated except the API key.

​
3. Enter your Operata API token

Paste an Operata API token into the API key parameter. Create one in the Operata console under Settings → Config → API. See the Operata help article for the full lifecycle.

​
4. Deploy the stack

Acknowledge the IAM resource creation and click Create stack. The stack reaches CREATE_COMPLETE in around five minutes. CloudFormation provisions:

​
5. (Optional) Tag the new resources

Apply your cost-allocation and ownership tags. See Tag your AWS resources.

​
6. Place a test contact through the bot

Trigger a call that routes to your Lex bot through an Amazon Connect contact flow. Interact by voice or DTMF as your flow expects. End the contact cleanly.

​
Verify

In the Operata console, open Calls and Logs → Summary and locate the test contact. The Lex conversation events appear within five minutes of contact end and join the Contact Trace Record (CTR) by ContactId. If nothing appears after five minutes, see Troubleshooting.

​
Data collected

Each event carries a Lex conversation log entry, including:
  • Session ID and bot identifiers.
  • Intent names and recognition confidence scores.
  • Slot values (subject to redaction).
  • Utterance text (subject to redaction).
  • Session attributes.
  • Fulfillment status and Lambda response data.
  • Conversation timestamps.
For the full Lex log schema, see the AWS Lex logging reference.

​
Privacy

Raw Lex logs contain customer utterances and slot values. The integration ships a redaction Lambda that runs in your AWS account before any log leaves AWS. See: Contact Operata Support for help selecting a redaction configuration.

​
Charges

All AWS service charges from this stack appear on your AWS bill. The Lex integration is included in every Operata plan at no Operata cost. Primary cost factors:
  • EventBridge event processing.
  • CloudWatch Logs data transfer out of CloudWatch.
  • Secrets Manager (rolled into the API destination charge).
You may incur additional AWS data-transfer charges for data leaving AWS to Operata.

​
Deploying alongside other stacks

The Lex stack runs independently of the CTR, Contact Lens, and contact-flow logs stacks. Add or remove any stack without affecting the others.