Error starting KVS Stream

[tdanwells]

the KVS does not want to initialize. All the logs show is the connect log generating the following. Where can we go to try and get more detail about the error? The lambda functions do not appear to be called as they are not generating any cloudwatch logs.

{ "Results": "Error", "ContactId": "3ef1b4bf-ac6c-47ac-96f5-d97bd1e70da6", "ContactFlowId": "arn:aws:connect:us-east-1:8redact:instance/5c253eredact-157607df22a8/flow-module/d81d5redact8ad8-61bf26c66547", "ContactFlowName": "VMX3-CoreFlowModule-ftcto9", "ContactFlowModuleType": "StartMediaStreaming", "Identifier": "Start KVS from customer only", "Timestamp": "2024-08-22T15:43:07.139Z", "Parameters": { "MediaStreamTypes": "Audio", "Track": "FromCustomer" }, "ModuleExecutionStack": [ "arn:aws:connect:us-east-1:8redact:instance/5c253e68-dd68-4credact07df22a8/flow-module/d81d572bredactc-8ad8-61bf26c66547", "arn:aws:connect:us-east-1:8redact:instance/5c253e68-dd68-4credactdf22a8/contact-flow/c5e59d4b-9redact8b-815c-71801be48eda" ] }

[jcnovoa]

While everything else is automated, enabling KVS is a manual step you have to complete in the deployed Amazon Connect instance you are working with:

[tdanwells]

Stream is set up and configured per the instructions. The problem appears when the start stream tool is called in the CoreFlow Module.

@.***

@.***

While everything else is automated, enabling KVS is a manual step you have to complete in the deployed Amazon Connect instance you are working with: KVS.PNG (view on web)https://urldefense.us/v3/__https:/github.com/user-attachments/assets/b6cc6409-0181-4660-98e6-fb3d5ef5cc91__;!!Az_Xe1LHMyBq19w!LvvUFMPTQ-Y7K2k8h8WuYAO4ND6wucSOEmA8mI8RFTm0xZmWs8pqnScKmE2z7jwBt0a1XyI7rfznLYfB8bBbYMx6c3MS$

— Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https:/github.com/amazon-connect/voicemail-express-amazon-connect/issues/26*issuecomment-2311392882__;Iw!!Az_Xe1LHMyBq19w!LvvUFMPTQ-Y7K2k8h8WuYAO4ND6wucSOEmA8mI8RFTm0xZmWs8pqnScKmE2z7jwBt0a1XyI7rfznLYfB8bBbYNOe1Fu5$, or unsubscribehttps://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/BKW2MXQWSQX2VTERYJP4SM3ZTPIWHAVCNFSM6AAAAABM6QV5CCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJRGM4TEOBYGI__;!!Az_Xe1LHMyBq19w!LvvUFMPTQ-Y7K2k8h8WuYAO4ND6wucSOEmA8mI8RFTm0xZmWs8pqnScKmE2z7jwBt0a1XyI7rfznLYfB8bBbYCsQrG3U$. You are receiving this because you authored the thread.Message ID: @.**@.>>

[dougjaso]

Can you share screenshots of the KVS config on your instance?

[AbdulQayyumaq]

Any resolution for this!

It's quite weird that i have done this for three amazon connect instances, there was no KVS initialization error for two of them but for third this start occurring.

[tdanwells]

Not yet. Same result here. Some instances work no problem and randomly, one that is set up the exact same will not.

From: AbdulQayyumaq @.> Sent: Wednesday, September 4, 2024 10:17 AM To: amazon-connect/voicemail-express-amazon-connect @.> Cc: Wells, Dan [US-US] @.>; Author @.> Subject: EXTERNAL: Re: [amazon-connect/voicemail-express-amazon-connect] Error starting KVS Stream (Issue #26)

CAUTION: This email originated from outside of Leidos. Be cautious when clicking or opening content.

Any resolution for this!

It's quite weird that i have done this for three amazon connect instances, there was no KVS initialization error for two of them but for third this start occurring.

— Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https:/github.com/amazon-connect/voicemail-express-amazon-connect/issues/26*issuecomment-2329349682__;Iw!!Az_Xe1LHMyBq19w!LACtC_enh9Gy7gYYy87HJ-RXJpNipE3GwxSRSwkOuzjMbBPcGXCpiNrlg-CqabO4hU5A-vuXQOFawSv1VodxmdYFCi9p$, or unsubscribehttps://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/BKW2MXRZ4SK2S532N7FOJNDZU4P6FAVCNFSM6AAAAABM6QV5CCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRZGM2DSNRYGI__;!!Az_Xe1LHMyBq19w!LACtC_enh9Gy7gYYy87HJ-RXJpNipE3GwxSRSwkOuzjMbBPcGXCpiNrlg-CqabO4hU5A-vuXQOFawSv1Vodxmbq-nn8Y$. You are receiving this because you authored the thread.Message ID: @.**@.>>

[dougjaso]

If streams are not initializing, and that is what you see in logs, then there is a larger Connect/KVS issue at play and a support case needs to be opened with AWS support. To be 100% clear, the first try on a brand new instance will always fail. And if you do the second too fast, it can fail too. If you have tried and minutes later it still cannot initialize a stream, then there is a KVS/Connect problem.

[sonymammen-vf]

Same result. Tested with 2 instances. Below screenshot summarizes all the config/results.

[dougjaso]

In your connect contact flow logs, is the stream initializing? Or is it failing?

[sonymammen-vf]

I got success in the Connect flow logs. I can see new 5 KVS streams getting created for the new tests I do.

The KVStoS3 lambda is still showing as "No Records Processed" . Since that lambda is not triggered. No logs for any of the VMX3 lambdas.

[dougjaso]

So not an error in starting KVS. Error is that these are not passing through the filter. In your voicemail setup, where are you putting the process? Are you just doing the normal test flow or are you starting VM from elsewhere, like a queue flow? Can you send me an email to setup a time to troubelshoot?

[dhesij]

Hi @dougjaso, having the same issue in that KVS to s3 Lambda is not getting triggered. Can you join a session to troubleshoot?

{ "ContactId": "f9ee50fd-860a-4310-8599-f32c6a1ef10c", "ContactFlowId": "arn:aws:connect:eu-west-2:442042540326:instance/ce472d01-9c86-4a6d-8356-44c452fc72d8/flow-module/b9a9a5a1-9454-4c3b-8e91-9ebdd90b444b", "ContactFlowName": "VMX3_Main_VM_Module_fignum-prod", "ContactFlowModuleType": "GetUserInput", "Identifier": "Wait for caller to record.", "Timestamp": "2024-09-26T16:05:49.411Z", "Parameters": { "TextToSpeechType": "ssml", "Timeout": "60000", "Text": "\n<break time=\"5s\"/>\n", "Voice": "Joanna", "MaxDigits": "1" }, "ModuleExecutionStack": [ "arn:aws:connect:eu-west-2:442042540326:instance/ce472d01-9c86-4a6d-8356-44c452fc72d8/flow-module/b9a9a5a1-9454-4c3b-8e91-9ebdd90b444b", "arn:aws:connect:eu-west-2:442042540326:instance/ce472d01-9c86-4a6d-8356-44c452fc72d8/contact-flow/0427afae-b2a6-4220-b508-cbb7e5b7f7e7" ] }

[dougjaso]

This issue was caused by using a customer-provided KMS key on the Kinesis Data Stream instead of the standard AWS Provided one. Customer-managed key has been added to the work list for the next release.