Troubleshooting Amazon Chime SDK meetings

The sections in this topic explain several ways to self-troubleshoot Amazon Chime SDK meetings.

Checking FAQs and known issues

Check these FAQs and lists of known issues on GitHub for troubleshooting and debugging advice.

Verifying network access

Enterprises often have network firewalls that restrict access to specific ports, or connections to IP address ranges out of their network. The following sections explain some of the ways you can verify network access.

Validating AWS SDK and Amazon Chime SDK subnets and ports

Applications that use the Amazon Chime SDK utilize two tiers, server and client. The server tier uses the AWS SDK and has server-side meeting handlers. The client tier uses client SDKs.

The AWS SDK is used to call server APIs such as CreateMeeting. Such APIs connect to the AWS global service endpoints in the us-east-1, us-west-2, ap-southeast-1, eu-central-1, us-gov-east-1, and us-gov-west-1 Regions. The AWS IP address ranges page in the AWS General Reference lists the IP address ranges for each Region. For information about service endpoints and quotas, see the Amazon Chime SDK endpoints and quotas.

Client SDKs, such as the Amazon Chime SDK for JavaScript, connect to service endpoints in the *.chime.aws domain.

Use the following validations to ensure that you have network permissions:

Using demo apps to reproduce issues

As a best practice, start the debugging process by trying to reproduce your issue in one of demo apps. That enables the service team to locate where the issue might be. If you can't reproduce the issue with a demo app, you can review the app's code to see how it implemented the relevant use case.

Using the Meeting Readiness Checker

Use the Amazon Chime SDK Meeting Readiness Checker on GitHub. The checker helps verify audio and video devices, and user connections. You can present the results to your end users with by using pass/fail statues that expose the root cause of any issues.