Amazon Elastic Kubernetes Service (EKS) vs. Amazon SageMaker

It is well suited when you want to have a Kubernetes cluster in AWS Cloud and want to avoid all the management overhead of maintaining your own cluster in terms of the control plane. EKS seems to be lacking in features when compared with AKS and GKE. Backups, service mesh, and monitoring have a lot of room for improvements.

Incentivized

Amazon SageMaker is a great tool for developing machine learning models that take more effort than just point-and-click type of analyses. The software works well with the other tools in the Amazon ecosystem, so if you use Amazon Web Services or are thinking about it, SageMaker would be a great addition. SageMaker is great for consumer insights, predictive analytics, and looking for gems of insight in the massive amounts of data we create. SageMaker is less suitable for analysts who do generally "small" data analyses, and "small" data analyses in today's world can be billions of records.

Incentivized

• Managed control plane
• Autoscaling

Incentivized

• Provides enough freedom for experienced data scientists and also for those who just need things done without going much deeper into building models.
• Customization and easy to alter and change.
• If you already are an Amazon user, you do not need to transition over to another software.

Incentivized

• AWSIAM integration with Kubernetes RBAC could be better.
• Enabling some add-ons like service mesh, and monitoring will be nice instead of having to install them yourself after the creation of the cluster.
• EKS bootstrap time could be faster ...

Incentivized

• The UI can be eased up a bit for use by business analysts and non technical users
• For huge amount of data pull from legacy solutions, the platform lags a bit
• Considering ML is an emerging topic and would be used by most of the organizations in future, the pipeline integrations can be optimized

Incentivized

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.

Incentivized

Amazon SageMaker comes with other supportive services like S3, SQS, and a vast variety of servers on EC2. It's very comfortable to manage the process and also support the end application by one click hosting option. Also, it charges on the base of what you use and how long you use it, so it becomes less costly compared to others.

Incentivized

• 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.

Incentivized

• We have been able to deliver data products more rapidly because we spend less time building data pipelines and model servers.
• We can prototype more rapidly because it is easy to configure notebooks to access AWS resources.
• For our use-cases, serving models is less expensive with SageMaker than bespoke servers.

Incentivized