Amazon Connect and Lambda logs: Error loading Log Streams

Error loading Log Streams

Trying to get your Lambda function logs to show up in Cloudwatch, but you keep getting an error loading log streams?

“There was an error loading Log Streams. Please try again by refreshing this page.”

Chances are, you are here because refreshing didn’t help. I ran into this issue as I was troubleshooting a Lambda function invoked from an Amazon Connect contact flow.

What are some troubleshooting steps you can try?

1.  Check service health

Check the service health status in your region from the official AWS service health dashboard.

Avoid Contact Center Outages: Plan Your Upgrade to Amazon Connect

Learn the six most common pitfalls when upgrading your contact center, and how Amazon Connect can help you avoid them.

Get the Guide

This step makes sense if your logs were showing up before, but you can’t get any of them to load right now. Further steps won’t help much in the unlikely event that Cloudwatch service, or any related service, is down in your region.

2.  Check permissions

If the logs never showed up there may be a problem with permissions. Lambda functions are not able to write logs by default, an administrator needs to grant Cloudwatch permissions to the role used for execution.

To check if that’s the case:

1. Navigate to the AWS Lambda Management Console, click on the function in question and check which execution role (IAM role) is used to run this function. 
2. Go to IAM management console and check permissions on that particular role. Do you have any permissions granted for the Cloudwatch service?
3. If not, you can start by attaching CloudwatchLogsFullAccess policy to your execution role.  This change will take effect almost immediately. 

If this was the root cause of your problem and the Lambda function was not able to write logs, you won’t be able to retrieve past logs. However, any new logs should start generating and showing in the Cloudwatch console. Also, if you need to ensure a more granular access you can do that later with a custom policy.

3.  Check limit

Check if you’ve hit the 5000 log groups per account per region limit or any other Cloudwatch limit here. Some limits can be increased by reaching out to AWS support.

Let me know if this helps through the comments below!

Ask for a demo or contact us here.