Amazon Chime SDK Implementation

As we all know Amazon has also entered in the world of Video calling service during the Covid Breakdown period.

With the entrance of Amazon Chime in the market of Video calling service the competition for being in the Top Video calling service has become more tough for Google Meetup, Zoom etc.

Since the Amazon chime service has been launched recently hence many developers face issues while implementing the Amazon Chime SDK service.

So here in this post I have discussed all the important points about implementing the Amazon Chime SDK from both front end and backend point of view.

Front end Side :

  1. React Sdk link :
  2. Javascript Sdk link :
  3. IOS Sdk link :
  4. Android Sdk Link :

Back end side (AWS SDK ):

For more information check out below link :

How to Create Meetings with the Amazon Chime SDK

Below are the steps which should be followed to create a meeting with the Amazon chime sdk. Before we begin, we must integrate our client application with an Amazon Chime SDK client library.

To create a meeting with Audio and Video

  1. Complete the following steps from your server application:
    1. Use the CreateMeeting API action in the Amazon Chime API Reference to create a meeting. Optionally, specify an AWS Region using the MediaRegion parameter. For more information about choosing a media Region, see Amazon Chime SDK media Regions.
    2. Add attendees to the meeting using the CreateAttendee API action or the BatchCreateAttendee API action. Securely transfer the meeting and attendee from your server application to the client authorized as the respective attendee. For more information about meetings and attendees, see Meeting and Attendee in the Amazon Chime API Reference.
  2. Complete the following steps from your client application:
    1. Use an Amazon Chime SDK client library to construct a MeetingSessionConfiguration object. Use the meeting and attendee information from the previous steps.
    2. Implement the AudioVideoObserver interface.
    3. Create a MeetingSession using the MeetingSessionConfiguration.
    4. Use the AudioVideoFacade from the MeetingSession to control real-time media.
      1. Register an instance of the AudioVideoObserver interface. This lets you receive events when the meeting state changes.
      2. Select initial devices for the audio input, audio output, and video input.
      3. Start the audiovisual session.
      4. Start local video capture when the user wants to share video.
      5. To show video tiles, manage video tile events, and bind the tiles to video surfaces in the client application.
      6. Manage other user interactions such as muting and unmuting, or starting and stopping local video capture.
      7. To leave the meeting, stop the audiovisual session.
    5. (Optional) Use the AudioVideoFacade from the MeetingSession to share media content, such as screen captures, with other clients.
      1. Start the screen share session. The content joins the meeting as an additional attendee.
      2. To view the shared content, manage video tile events and bind the tiles to surfaces in the client application.
      3. Manage other interactions, such as pausing, restarting, or stopping the content share.

The meetings end when you run the DeleteMeeting API action. A meeting automatically ends after a period of inactivity, such as the following:

  • No audio connections are present in the meeting for more than five minutes.
  • Less than two audio connections are present in the meeting for more than 30 minutes.
  • Screen share viewer connections are inactive for more than 30 minutes.
  • The meeting time exceeds 24 hours.

React code :

Leave a Comment

Your email address will not be published. Required fields are marked *