AWS Connect delivers contact trace recording very slow

Question

I have setup AWS Connect -> kinesis firehose -> S3
However it took like 5-10 mins to create CTR in S3 bucket while in contact lens show the record is completed.
How do we improve this siltation? Thanks

Accepted Answer

Hello, first of all here you can see when a contact record is generated: [Events in the contact record](https://docs.aws.amazon.com/connect/latest/adminguide/about-contact-states.html#ctr-events). Until the agent interaction is not finished the CR won't be generated.

When the CR is generated is transmitted either to **Kinesis streams** or to **Kinesis firehose**, depending on your configuration. (See [Enable data streaming for your instance](https://docs.aws.amazon.com/connect/latest/adminguide/data-streaming.html)).

**In your case, as you are using firehose**, this service introduce a buffer time between 60 and 900 seconds: [Firehose data frequency delivery](https://docs.aws.amazon.com/firehose/latest/dev/basic-deliver.html#frequency). You can change the buffer time and interval settings to reduce this latency to a minimun of 60 seconds.

**If you need to reduce further this latency** then you should use **Kinesis streams** as the target of your contact records stream. A possible architecture here is to use a lambda to consume each record and to write directly into S3: [Using AWS Lambda with Amazon Kinesis](https://docs.aws.amazon.com/lambda/latest/dg/with-kinesis.html#services-kinesis-params). With this configuration you will reduce to just some seconds the total latency of the CRs appearing in your S3 bucket.

Answer

Thank for your reply. Any possibility to not using lambda which is from kinesis stream directly to  S3 without lambda/firehose?

Answer

**Contact records** are only exported using Kinesis. And for using the data in a **kinesis stream** you need always a consumer.

Here you can see the full list of possible Kinesis consumers: [Reading Data from Amazon Kinesis Data Streams](https://docs.aws.amazon.com/streams/latest/dev/building-consumers.html). One common alternative for using lambda would be to leverage the [Kinesis Client Library](https://docs.aws.amazon.com/streams/latest/dev/shared-throughput-kcl-consumers.html) in a container or instance based solution.

**I would also recommend** to have a look at the list of [Connect APIs](https://docs.aws.amazon.com/connect/latest/APIReference/API_Operations.html) (specially the Get and List), where you can obtain information with just an API call (so Kinesis is not needed here). For example the [Connect Real-time metrics](https://docs.aws.amazon.com/connect/latest/adminguide/real-time-metrics-definitions.html) can be obtained in real-time using the [GetCurrentMetricData](https://docs.aws.amazon.com/connect/latest/APIReference/API_GetCurrentMetricData.html) API. If the information that you need can be obtain from those APIs this would be a way to avoid using Kinesis and lowering the total latency.

AWS Connect delivers contact trace recording very slow

Relevant content