Control Plane is now a technology partner of Akamai Cloud. You can add regions from Akamai Cloud to your Global Virtual Cloud in Control Plane. And by leveraging Control Plane’s Universal Cloud Identity, workloads running on Akamai Cloud regions can still consume any service of AWS, GCP, or Azure with no credentials embedded in the workload.
“Modern enterprise architectures demand flexibility, not walled gardens. Partnering with Control Plane allows our mutual customers to place workloads precisely where they deliver the most business value—combining Akamai’s massive global edge reach with cross-cloud failover and seamless service access across other cloud providers.”
– Zak Putnam AVP, Global Cloud Partnerships | Akamai Cloud
Joining Akamai Cloud to Control Plane
You can create Kubernetes clusters using the Control Plane Managed K8s Service (MK8s) or you can use Akamai’s own K8s service, LKE, to treat one or multiple Akamai virtual machines as one logical deployment target. For an LKE cluster created in Akamai’s console, Control Plane generates a single kubectl command that installs an agent into it. The cluster then registers as a location in your org — one you add to a GVC alongside your existing ones. Any workload you target at that location now deploys onto Akamai, with the same deployment surface, service mesh, firewalls, and tamper-proof audit trail as every other location you’ve connected. (Docs: bringing your own Kubernetes cluster.)
“Our partnership with Akamai Cloud adds reach and economics no hyperscaler matches at the edge. With Control Plane, a company can run compute on Akamai Cloud and still access any hyperscaler service they want. They can also failover to any cloud provider thus gaining better performance, cost, as well as resiliency.”
– Doron Grinstein | CEO, Control Plane
Leveraging Universal Cloud Identity
You can assign a workload in an Akamai location an identity, and through Universal Cloud Identity, it consumes services from your AWS, GCP, and Azure accounts under least-privilege rules, with no credentials stored in the workload. (Docs: cloud provider access.)
So a container running on Akamai Cloud can query BigQuery in GCP, pull from an SQS queue in AWS, or authenticate against Entra ID in Azure.
The workload doesn’t need to know the services aren’t local. From the application’s point of view it’s one cloud. This gives Akamai Cloud customers the ability to leverage the full ecosystem of any hyperscaler service without workarounds like a long-lived key in a config map.
Why Akamai Cloud
Akamai runs an edge network of more than 4,350 points of presence across 130+ countries, and since completing its acquisition of Linode in March 2022 it has been building that footprint into a full cloud computing platform — one Akamai describes as the world’s most distributed cloud.
Our partnership with Akamai enables companies to run compute wherever it makes the most sense on whatever cloud offers the most value and functionality while still leveraging best of breed services.