Amazon Elastic Kubernetes Service (Amazon EKS) is a managed container service to run and scale Kubernetes applications in the cloud or on-premises, available on AWS or on-premise through Amazon EKS Anywhere.
$0.10
per hour of each cluster created
SUSE Rancher
Score 8.0 out of 10
N/A
Developed by Rancher Labs and now from SUSE, Rancher is open-source software that enables organizations to deploy and manage Kubernetes at scale, on any infrastructure across the data center, cloud, branch offices, and the network edge. Rancher centrally manages Kubernetes clusters across the organization in order to ensure security and accelerate transformation. Rancher is also available hosted. Hosted Rancher is a fully managed Rancher control plane - presented as the fastest, most cost…
$7,594.99
per year up to 500 nodes
Pricing
Amazon Elastic Kubernetes Service (EKS)
SUSE Rancher
Editions & Modules
Amazon EKS Cluster
$.10
per hour of each cluster created
Subscription license
7,594.99
per year up to 500 nodes
Standard Subscription
11,234.99
per year 10 nodes
Priority Subscription
30,514.99
per year 10 nodes
Management Server Priority Subscription
41,830.99
per year 1 instance
Offerings
Pricing Offerings
Amazon EKS
SUSE Rancher
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Elastic Kubernetes Service (EKS)
SUSE Rancher
Features
Amazon Elastic Kubernetes Service (EKS)
SUSE Rancher
Container Management
Comparison of Container Management features of Product A and Product B
Well suited for microservices architecture but can be a bit costly if less number of microservices or monolithic architecture hosted to be hosted on containers. Use of hybrid cluster instances also works well using both normal and fargate instances. Also the integration of audit and diagnostic logs of master nodes helps to reduce the unwanted access related issues.
SUSE Rancher as a management tool becomes useful on a larger scale. Small deployments not so much. If someone also requires Kubernetes capacity or storage, Rancher is an excellent choice. Also, without Kubernetes' skills, it is unlikely that Rancher deployment is going to be a success. Then again if someone else is managing your Kubernetes capacity, setting up the software's capacity will yield greater control. Rancher is not a very integrated solution similar to others in the market.
No possibility to snapshot Projects. You can snapshot and restore the whole Kubernetes cluster, but not a Project or Namespace. For this, you have to use external tools.
You cannot detach the Rancher-created Kubernetes clusters from Rancher management.
Overall it deserves an 8 out of 10. The platform is very easy to use as long as the UI is stable. We have had a few buggy versions in the past. However the CLI is excellent and the platform is simple to manage and maintain. It is easy to deploy and offer for company wide use which increases utilization and ROI.
The documentation is quite complete and there is a very active community that is willing to collaborate and answer questions for those who are just starting out.
It feels like AWS is behind the EKS race, the only advantage I'm able to see right now is the support of IPv6, however, trying to promote AWS alternatives that are different from the market and more like a vendor locking solutions like ECS/Fargate have kept AWS behind and focusing on the wrong things. EKS needs to really improve its integration with the Kubernetes ecosystem and have an enterprise solution for monitoring, backups, and service mesh.
SUSE Rancher is an excellent choice for managing multiple Kubernetes clusters, especially when catering to different teams with distinct access rights and requirements. It allows us to deploy these clusters on-premises across various sites or in the cloud. However, if you’re dealing with only one or a few Kubernetes clusters, using SUSE Rancher might introduce unnecessary complexity. This is where EKS wins, as its native cloud based abilities are better suited to scale, support higher complexity and larger demand.
Migrating all our workloads from ec2 VMs to containers running in Kubernetes has been a huge improvement for the management and resilience of our Infrastructure.
EKS Upgrade process to a new version seems to be taking very long ....
EKS creation time usually takes over 10 minutes in us-east-1, we would like faster creation times to be under 5 minutes.
Shortens "Time-to-Market" factor for new business applications or implementing new functionalities. From 1 to 50 microservices-based business applications in 6 years.
24/7 availability, generates more money. There are many infrastructure components that are regularly powered-off for maintenance or upgrade, bur we rarely are turning off our downstream Kubernetes clusters where our business applications lives.
Single Point of Contact with platform maintenance and development Team, eases implementation of new business applications
