

However, some webhooks expect JSON key-value pairs that Amazon SNS doesn't support when confirming the HTTP or HTTPS subscription.įor example, Amazon Chime webhooks expect a JSON request with a message string corresponding to a "Content" key. (Yes, the Amazon Chime SDK is different - we'll get to that in a bit.You can use Amazon SNS to send notification messages to HTTP or HTTPS endpoints, such as webhook URLs. This is the general SDK that's used for most of the stuff you can do on the AWS platform. To successfully create and run an online meeting on Chime essentially requires two steps:Ĭreating the actual Chime meeting is done using the AWS SDK.

This means that you don't have to think about how much infrastructure to prepare to potentially support so and so amount of users all of it just automatically adjust and scale for you.Īt the time of this writing, the pricing for the Amazon Chime SDK is also very cost-effective: it amounts to just USD 0.0017 / minute connected for every attendee. It does a great job of abstracting a lot of the details away, so you (as the developer) won't have to deal too much about the intricacies of working with websockets, WebRTC, and media handling.Įven better, you don't need to create servers and storage to support your users - the technology resources required to run your meetings are automatically managed for you. The Amazon Chime SDK allows you to create managed online meetings where attendees can do simultaneous audio and video streaming, as well as share content across all attendees (e.g. So, in the spirit of discovery, wonder, and that itch to build, I spent a bit of time working with the Amazon Chime service to get a better feel of what it has to offer. Now, I use Slack very significantly in my day-to-day, and Slack already has voice and video calls available, so actively migrating that functionality over to a different platform feels like a really major move. While the decision to adopt or strengthen their AWS posture isn't exactly something new for a lot of companies, the real standout for me was that Slack will also migrate their voice and video call functionality to use the Amazon Chime service moving forward.

I was one of those people that were pleasantly surprised, waking up one morning earlier this month, to the news of Slack announcing a partnership with AWS.
