AWS approach – as a solution provider – is based on the core belief that customers are best served through a model which provides the highest possible level of abstraction to the user (whether an operator or a developer). The AWS strategy is to handle technical complexity “behind the curtain”, enabling the customer to maximize productivity (and speed innovation) through its cloud-native services such as Fargate and Lambda. This model departs from the more open Kubernetes approach, which can require the customer to have greater expertise (and take on more work for delivery), but which in turn allows the customer more flexibility and control. Note that this analysis specifically addresses the portions of the AWS solution portfolio for operating with Kubernetes-orchestrated containers. While some (limited) mention is made of the AWS-native services, these are not the focus of this Guide.
Container management vendors tend to address the opportunity in one of two ways: container management platform vendors approach the market for managing Kubernetes-orchestrated clusters with an environment-agnostic mindset, i.e., the solution is essentially the same regardless of whether the Kubernetes clusters are operating in a public cloud, on premises or at the edge, and regardless of whether delivered as platform (customer-managed) or service (vendor-managed). By contrast, cloud service providers (CSPs), believing that economics will drive all workloads eventually to the public cloud, deliver solutions for Kubernetes-managed clusters as an extension to their native cloud services.
This approach enables the deployment of Kubernetes clusters both in the cloud and on premises but relies on the vendor’s public cloud – and managed service model – for central management, security, and value-added services. As a result, functionality is deployed in solution configurations with different tiers of functionality, manageability and/or support depending on where the Kubernetes clusters are operating, with the highest functionality in the CSP’s cloud, and more limited capabilities elsewhere (i.e., on-premises, or on another CSP’s cloud infrastructure or Kubernetes service).
AWS Container Management Product Brief Includes:
Download the full product brief now!