In an AWS re-Invent Leadership session titled “AWS Wherever You Need It,” [1.] Wayne Duso, vice president of engineering and product at AWS, expressed similar goals. “Today, customers want to use AWS services in a growing range of applications, operating wherever they want, whenever they require. And they’re striving to do so to deliver the best possible customer experience they can, regardless of where their customers or users happen to be located. One way AWS helps customers accomplish this is by bringing the AWS value to our regions, to metro areas, to on-premises, and to the furthest and evolving edge.”
Note 1. You can watch the 1 hour “AWS Wherever You Need It” session here (top right).
“We’re helping customers by providing the same experience from cloud to on-prem to the evolving edge, regardless of where your application may need to reside,” Duso explained. “AWS is enabling customers to use the same infrastructure, services and tools to accomplish that. And we do that by providing a continuum of consistent cloud-scale services that allow you to operate seamlessly across this range of environments.”
Duso explained how AWS is enabling edge computing by adding capabilities for mobile and IoT devices. “There are more than 14 billion smart devices in the world today. And it’s often in things we think about, like wristwatches, cameras, cellphones and speakers,” he said.
“But more often, it’s the stuff that you don’t see every day powering industries of all types and for all types of customers.” Duso cited the example of Hilcorp, a leading energy producer, which is using smart devices to monitor the health of its wells, optimize production and proactively predict failures so it can minimize capital expenditures.
With IoT devices becoming common among energy providers, edge computing is on the rise to handle the volume of data these devices generate. “Now, AWS IoT provides a deep and broad set of services and partner solutions to make it really simple to build secure, managed and scalable IoT applications,” Duso added.
Duso pointed to Couchbase as a use case for flexible AWS services: “Couchbase is a non-SQL database company that uses AWS hybrid edge services such as Local Zones, Wavelength, Outposts and the Snow Family to deploy its applications and highly scalable, reliable and performant environments to reduce latency by over 18 percent for its customers.” Each of these AWS managed services enables Couchbase to move data from the edge to the cloud or manage and process it where it’s generated.
“What we built on these AWS compute environments was a highly distributed, managed or self-managed database,” Duso explained. “For the cloud, an internet gateway for accessing that data securely over the web and synchronizing that data down to the edge. And that works across cloud, edge and on the offline, first-compute environments.”
“Our goal is I want to make AWS the best place to run 5G networks. That is the overarching objective. How can I make AWS, whether we are running it in the region, in a Local Zone, on an Outposts, on a Snow device, how do we make it the best place to run a 5G network, and then provide that infrastructure.”
AWS’ 5G network efforts include a cloud architecture that can support an operator’s 5G SA core network and applications, similar to what AWS is doing with greenfield U.S. wireless network operator Dish Network. Sidd Chenumolu, VP of technology development and network services at Dish Network, recently explained that the wireless carrier’s 5G core network was using three of AWS’ four public regions, was deployed in “multiple availability zones and almost all the Local Zones, but most were deployed with Nokia applications across AWS around the country.”
AWS is also working with Verizon to support a part of that carrier’s public MEC system. This includes use of AWS’ Outposts and Wavelengths, the latter of which AWS recently expanded in the United Kingdom with Vodafone.
Hofmeyr continued, “I think you have a spectrum (of different wireless carrier networks), from the total greenfields like what we did with Dish to the large tier-ones. The one thing that’s common across the board is the desire to modernize and become more cloud-like. That is common. Everyone wants that. Each one has a very unique job. There’s not one way that they all are executing in the same way. They’re taking this one workload and then building, so all of them are focusing on different workloads in the network and put it in the cloud.”
In conclusion Hofmeyr said, “I think all over the edge we find these use cases for which purpose-built systems were designed to handle that. And our goal is how do you make that available in the cloud.”