Personal blog of Yzmir Ramirez

AWS today announced a number of IoT-related updates that, for the most part, aim to make getting started with its IoT services easier, especially for companies that are trying to deploy a large fleet of devices. The marquee announcement, however, is about the Alexa Voice Service, which makes Amazon’s Alex voice assistant available to hardware manufacturers who want to build it into their devices. These manufacturers can now create “Alexa built-in” devices with very low-powered chips and 1MB of RAM.

Until now, you needed at least 100MB of RAM and an ARM Cortex A-class processor. Now, the requirement for Alexa Voice Service integration for AWS IoT Core has come down 1MB and a cheaper Cortex-M processor. With that, chances are you’ll see even more lightbulbs, light switches and other simple, single-purpose devices with Alexa functionality. You obviously can’t run a complex voice-recognition model and decision engine on a device like this, so all of the media retrieval, audio decoding, etc. is done in the cloud. All it needs to be able to do is detect the wake word to start the Alexa functionality, which is a comparably simple model.

“We now offload the vast majority of all of this to the cloud,” AWS IoT VP Dirk Didascalou told me. “So the device can be ultra dumb. The only thing that the device still needs to do is wake word detection. That still needs to be covered on the device.” Didascalou noted that with new, lower-powered processors from NXP and Qualcomm, OEMs can reduce their engineering bill of materials by up to 50 percent, which will only make this capability more attractive to many companies.

Didascalou believes we’ll see manufacturers in all kinds of areas use this new functionality, but most of it will likely be in the consumer space. “It just opens up the what we call the real ambient intelligence and ambient computing space,” he said. “Because now you don’t need to identify where’s my hub — you just speak to your environment and your environment can interact with you. I think that’s a massive step towards this ambient intelligence via Alexa.”

No cloud computing announcement these days would be complete without talking about containers. Today’s container announcement for AWS’ IoT services is that IoT Greengrass, the company’s main platform for extending AWS to edge devices, now offers support for Docker containers. The reason for this is pretty straightforward. The early idea of Greengrass was to have developers write Lambda functions for it. But as Didascalou told me, a lot of companies also wanted to bring legacy and third-party applications to Greengrass devices, as well as those written in languages that are not currently supported by Greengrass. Didascalou noted that this also means you can bring any container from the Docker Hub or any other Docker container registry to Greengrass now, too.

“The idea of Greengrass was, you build an application once. And whether you deploy it to the cloud or at the edge or hybrid, it doesn’t matter, because it’s the same programming model,” he explained. “But very many older applications use containers. And then, of course, you saying, okay, as a company, I don’t necessarily want to rewrite something that works.”

Another notable new feature is Stream Manager for Greengrass. Until now, developers had to cobble together their own solutions for managing data streams from edge devices, using Lambda functions. Now, with this new feature, they don’t have to reinvent the wheel every time they want to build a new solution for connection management and data retention policies, etc., but can instead rely on this new functionality to do that for them. It’s pre-integrated with AWS Kinesis and IoT Analytics, too.

Also new for AWS IoT Greengrass are fleet provisioning, which makes it easier for businesses to quickly set up lots of new devices automatically, as well as secure tunneling for AWS IoT Device Management, which makes it easier for developers to remote access into a device and troubleshoot them. In addition, AWS IoT Core now features configurable endpoints.

Last year, Amazon announced a new initiative, Alexa for Business, designed to introduce its voice assistant technology and Echo devices into a corporate setting. Today, it’s giving the platform a big upgrade by opening it up to device makers who are building their own solutions that have Alexa built in.

The change came about based on feedback from the existing organizations where Alexa for Business is today being used, Amazon says. The company claims thousands of businesses have added an Amazon Echo alongside their existing office equipment since the program’s debut last year, including companies like Express Trucking, Fender and Propel Insurance, for example.

But it heard from businesses that they want to have Alexa built in to existing devices, to minimize the amount of technology they need to manage and monitor.

The update will allow device makers building with the Alexa Voice Service (AVS) SDK to now create products that can be registered with Alexa for Business, and managed as shared devices across the organization.

The device management capabilities include the ability to configure things like the room designation and location and monitor the device’s health, as well as manage which public and private skills are assigned to the shared devices.

A part of Alexa for Business is the ability for organizations to create their own internal — and practical — skills for a business setting, like voice search for employee directories, Salesforce data or company calendar information.

Amazon also recently launched its own feature for Alexa for Business users that offers the ability for staff to book conference rooms.

Amazon says it’s already working with several brands on integrating Alexa into their own devices, including Plantronics, iHome and BlackBerry. And it’s working with solution providers like Linkplay and Extron, it says. (Citrix has also begun to integrate with the “for Business” platform.)

“We’ve been using Alexa for Business since its launch by pairing Echo devices with existing Polycom equipment,” noted Laura Marx, VP of Alliance Marketing at Plantronics, in a statement about its plans to make equipment that works with Alexa. “Integrating those experiences directly into products like Polycom Trio will take our customer experience to the next level of convenience and ease of use,” she said.

Plantronics provided an early look at the Alexa experience earlier this year, and iHome has an existing device with Alexa built in – the iAVS16. However, it has not yet announced which product will be offered through Alexa for Business.

It’s still too soon to see how well any of Amazon’s business initiatives with Alexa pay off — after all, Echo devices today are often used for consumer-orientated purposes like playing music, getting news and information, setting kitchen timers and making shopping lists. But if Amazon is able to penetrate businesses with Echo speakers and other Alexa-powered business equipment, it could make inroads into a profitable voice market, beyond the smart home.

But not everyone believes Alexa in the workplace is a good idea. Hackers envision how the devices could be used for corporate espionage and hacks, and warn that companies with trade secrets shouldn’t have listening devices set around their offices.

Amazon, however, is plodding ahead. It has even integrated with Microsoft’s Cortana so Alexa can gain access to Cortana’s knowledge of productivity features like calendar management, day at a glance and customer email.

The Alexa for Business capabilities are provided as an extension to the AVS Device SDK, starting with version 1.10, available to download from GitHub.