Close
Close

Published

Vapor IO links to AWS at the edge – operators need to do the same

The biggest question facing operators as they devise their strategies for edge computing is whether the cloud giants will be competitors or partners. In the centralize cloud, the scale of Amazon AWS and Microsoft Azure is hard to beat, but as the cloud is distributed to ever-more dispersed locations, the distributed nature of a telco’s network and sites mean it has more to bring to the table.

An operator might partner with AWS or Azure, providing locations and high quality connectivity while the cloud company brings its services and brand. As services become more personalized and differentiated, the operator might increase its place in the value chain by supporting network slicing from data center to edge. Those slices might call up resources from multiple networks and multiple clouds, helping to push the webscalers down the value chain.

There is still a major risk though. The webscale companies are better skilled than most telcos at managing advanced digital platforms and they have better brand relationships with consumers and businesses. In a compex, sliced environment they might well be the parties to seize control of the orchestration of the slices, reducing the the operator’s assets of sites, connections and spectrum to mere plumbing.

But if the operators do not partner, they face a head-to-head battle. They would be well placed to dominate edge-based services for their own existing consumer bases – using their central offices or cell sites to deliver personalized, high quality video over low latency connections, for instance. These are services they already offer, and the relationships with content providers like Netflix are relatively well established. Increasingly, Netflix, Amazon and others are not content to be purely over-the-top but are investing in infrastructure such as content delivery networks (CDNs), directly or through alliances with operators.

However, the biggest market and biggest source of growth in edge computing will be in the enterprise, industrial and IoT sectors, where the edge location will less commonly marry up with the telcos’ sites – many will be on-premises, which means MNOs will regret their failure to invest in better indoor coverage. Here, the established relationships are often with the cloud providers, and Amazon and Microsoft have been very active in getting affordable, deployable edge nodes into their corporate bases.

Also, if the operators snub the webscalers, they may see other companies stepping into the breach, providing sites and connectivity on a neutral host basis, aided by the rise of shared spectrum. Some of the tower operators and the wholesale fiber providers are interested in the idea of adding edge nodes to their neutral host infrastructure portfolio, leveraging their existing locations to emulate the model of a company like Equinix in the cloud data center.

Crown Castle has been the most active of the towercos in this regard, and has worked closely with a neutral host edge infrastructure start-up, Vapor IO. Now Vapor is showing the way that, we believe, the telcos and neutral hosts will need to go at the edge – working with AWS and Azure, not against them.

Vapor IO said it now offers a direct connection between its edge computing nodes, called Kinetic Edge – many of them located in Crown Castle sites and supported by Crown’s fiber – and AWS’s cloud data centers. A “straight fiber line” from a Vapor micro-data center to the AWS cloud would reduce latency and make it easier for customers to decide, on the fly, which data needs to be processed and stored locally and which needs to be sent to the central repository. Developers will have access to the full suite of AWS cloud services and can create applications which split workloads between the edge and the central cloud.

The service was jointly developed with Crown Castle and initially uses the towerco’s high speed Cloud Connect fiber-based links, which support one or more links of 50Mbps to 500Mbps, to implement AWS Direct Connect, which Amazon offers as a private connection from a customer’s location to the AWS cloud services. This is an alternative to routing traffic to AWS over a public Internet connection.

Another option for this kind of alliance in future might be SiteWise, a way to link industrial and IoT gateways to the AWS cloud, which can be run on edge servers, third party gateways, or Amazon’s own edge box, AWS Snowball.

“Over the past two years, we’ve been working very closely with Vapor IO to build out their Kinetic Edge using our real estate and fiber assets in many US cities,” added Phil Olivero, VP of technology at Crown Castle. “Chicago, the world’s first Kinetic Edge city, proved to be the ideal location for us to connect the Kinetic Edge directly to AWS. As Vapor IO rolls out the Kinetic Edge to new cities, we plan to extend our Cloud Connect to also connect to AWS in those locations. This will empower our mutual customers to build high-performance edge-enabled mobile applications using AWS.”

Vapor IO’s CEO Cole Crawford claimed that the connection will be like a hotline for developers, ensuring a high speed path between the smaller firm’s localized computing services and Amazon’s centralized ones.

That will unlock new applications that are best run by splitting workloads and data between the mobile edge and centralized locations, delivering a seamless end-to-end experience.

“By directly connecting AWS services to applications at the Kinetic Edge, we’re bringing the full power of the cloud to the last mile wireless network, delivering the foundation of a true edge-to-core architecture for developers,” said Crawford.

Despite the closeness to Crown Castle, Vapor IO is likely to develop similar capabilities with other site and fiber partners. It also has agreements with other tower companies, like SBA, to locate its edge hardware on their sites, and Crawford said it would work with other fiber owners, like Zayo, to ensure its growing network of micro-data centers always has connectivity to AWS.

And the firm acknowledged earlier this year that, despite its close ties to towercos, their sites did not always align well with all the edge services required. Crawford told LightReading that it was “not relevant to talk about sitting at the bottom of one tower”, but instead to focus on “tower-aggregated and connected, not tower-located” scenarios. In fact, the firm’s first edge data center in Chicago is in a DAS hub which, unlike some cell towers, has significant amounts of fiber. Another edge neutral host, EdgeMicro, has also moved away from the idea of building its nodes at the base of cell towers, because there is often insufficient fiber.

One company which voiced support for the Vapor IO announcement was another start-up, Network Next, which recently raised seed funding of $4.4m to work on edge-based mechanisms to speed up online and mobile gaming services by reducing latency. It works with game creators and content delivery networks, and CEO Glenn Fiedler commented: “Our customers run a massive number of game servers on AWS and we work with them to improve performance for mobile clients. As gaming companies increasingly look to bring high speed multiplayer games like Fortnite to mobile platforms, our sophisticated edge processing connects players back to AWS in the most optimal fashion, giving a true edge-to-core experience.”

This example shows the budding complexity of the edge cloud landscape, with many types of company looking for well-positioned, neutral host infrastructure on which to run their edge services – but also needing very good connectivity back to the central cloud.

In February, Vapor IO created the Kinetic Edge Alliance, looking to accelerate the spread of its particular architectural approach, which supports multiple micro-data centers spread across a city, which can be combined into a single virtual facility with citywide coverage using software-defined interconnection. The firm itself plans to have 80 such cities in play by the end of next year, but progress could be even faster with a broader ecosystem, and even if third parties licensed the architecture for their own build-outs.

Crawford said at the time: “We built Kinetic Edge for edge-native applications, which are more mobile and far more localized in their latency sensitivities … We wanted to create these hyper-local availability zones. We do that with multi-tenant shared infrastructure, and a software-defined mesh network, and by aggregating 10s, 30s, 100s of microcells into these PoPs [points of presence], which allows you to create a much more resilient, highly available architecture than if you were trying to create all of this in one building.”

The new Alliance’s initial members include five deployment partners and six technology partners. Among the recruits are:

  • The Deutsche Telekom spin-off, MobiledgeX, which is part of several open and standards efforts around the enterprise edge; and shows how a telco can, with some creative thinking, still have a strong role at the edge – by moving up the software and services stack rather than relying on physical locations and connectivity alone. It will provide automated workload orchestration tooling for provisioning and managing applications at the edge location nearest to a requesting device.
  • Federated Wireless, the most advanced of the spectrum access system (SAS) providers for the USA’s shared CBRS band. Shared spectrum is a key driver for deployment of private enterprise ‘sub-nets’, which can be built to support specialized enterprise needs, especially indoors; to provide multi-operator services; and, increasingly, to integrate edge computing with the local core and small cell RAN. For the KEA, Federated will bring software and systems for delivering 4G and 5G connectivity over CBRS to Kinetic Edge locations, including a set of pre-integrated wireless access points, end devices, and network functionality partners.
  • Packet, which provides a bare metal edge cloud platform and has cooperated with Vapor IO and others on producing the Open Glossary of Edge Computing under the auspices of the Linux Foundation.
  • Linode, which will extend its cloud computing infrastructure at Kinetic Edge locations.
  • StackPath, provider of an edge computing services platform called EdgeEngine, which will now support Kinetic Edge, enabling developers to deploy containers and virtual machines, as well as serverless scripts.

The technical partners will make their enabling technologies available for Kinetic Edge deployments. These include:

  • Alef Mobitech, with its edge architecture for MEC
  • Detecon International, another subsidiary of Deutsche Telekom, which focuses on edge as deployed by operators with 5G.
  • Hitachi Vantara, which provides technologies for data center infrastructure, edge-to-cloud data governance, and data-driven insights, including its Lumada platform for managing and acting on data from disparate sources.
  • New Continuum, which will cross-connect its West Chicago data center with the Kinetic Edge to provide local colocation capacity and a software-enabled internet exchange point (IXP).
  • n 19 IT equipment in Kinetic Edge Locations.
  • Pluribus Networks, whose network fabric for distributed cloud can span multiple Kinetic Edge (and non-Kinetic Edge) sites, and manage them as one fabric. It supports fabric-wide automation, multi-tenancy, granular telemetry and low latency network slicing, says the company.
  • Storage veteran Seagate, which will provide technical blueprints and deployment support for storage at the edge.

For the KEA as a whole, the thinking is that a joint effort by a variety of partners, which can offer an end-to-end solution based on pre-selected and pre-integrated elements, will give the edge computing market a shot in the arm, and place their offerings at the heart of that accelerated uptake.

Deployment partner companies will jointly roll out equipment and services, integrating their respective elements with the Kinetic Edge and coordinating their build-outs so that the resulting infrastructure platform is uniform and well integrated, and makes it easy to deploy new applications.

Only this multi-partner approach will address all the requirements, said Crawford, claiming: “It takes a village. It takes a number of companies building this.”

The initial focus is on the USA, and in particular on reaching 30 large metropolitan markets. The first markets, to be deployed under the auspices of the KEA this year, are Chicago, Pittsburgh, Atlanta, Dallas, Los Angeles, and Seattle. Chicago is already Vapor IO’s first city of deployment, mainly in partnership with Crown Castle – two of its sites are online there and a third will be added over the next two months.

Since the 30 metros cover about 50% of the population, that would result in true critical mass for edge computing; attracting a broad developer and enterprise ecosystem and ensuring most industries had neutral host edge sites in easy reach. That would also reduce the first-stage cost and risk for industrial adopters, while allowing them to start their deployment on a Kinetic Edge platform and then extend it indoors for particular low latency or high security applications.

This approach could help to ensure that the cloud giants do not snap up the entire enterprise edge market for themselves. So the cloud giants are not present in Kinetic Edge (or many of the edge computing alliances). Nor, with the exception of Deutsche Telekom’s two units, are the telcos. In time, however, both groups may find it advantageous to link up with initiatives like KEA – to reduce their own infrastructure costs by riding on a neutral host platform, rather than insisting on the kind of exclusive ownership which has been such a barrier to another activity which requires build-out in many locations, small cells.

Failure to share networks or rely on neutral hosts has been a significant brake on small cell proliferation. Operators should learn from that experience and be prepared to share the burden at the edge, and recognize that it will be services and orchestration that give them pole position in any value chain, not just physical sites.

Close