Amazon SageMaker Reviews

Amazon SageMaker is a collaborative tool for our data science projects. It allows us to integrate efficiently, write and review code, and access all the necessary project tools.

Amazon SageMaker is highly valuable for managing ML workloads. It connects to AWS cloud resources, making it easy to deploy algorithms and collaborate using tools like GitLab. It offers a wide range of Python libraries and other necessary tools for modeling and algorithms.

Amazon SageMaker can make it simpler to manage the data flow from start to finish, such as by integrating data, usingthe machine, and deploying models. This process could be more user-friendly compared to other tools. I would also like to improve integration with Bedrock and the LLM connection for AWS.

I have been using Amazon SageMaker for the past two years.

I've never encountered issues with SageMaker's scalability. AWS provides all the necessary resources in terms of power and capacity.

The initial setup is straightforward. We have a team from the infrastructure department that ensures the system runs smoothly. The data science team also plays a role in monitoring the effectiveness of the models. The deployment process usually takes two to three months for the whole project, with various strategies involved. SageMaker integrates well with AWS features, and when deploying, I typically set up APIs to make the model accessible to other systems and connect it with GitLab for easier model control.

In terms of pricing, I'd also rate it ten out of ten because it's been beneficial compared to other solutions.

I would rate Amazon SageMaker a nine out of ten because while it has all the necessary features, there could be improvements in making the data flow more manageable.

Our primary use case is to build machine learning models and manage them using Amazon SageMaker. We use various tools provided by SageMaker, such as the studio for machine learning, pre-processing data using Wrangler, and deploying models. Some users prefer using Jupyter notebooks for their own libraries while others use features like Jumpstart or Autopilot.

One of the most valuable features of Amazon SageMaker for me is the one-touch deployment, which simplifies the process greatly. Additionally, I appreciate the flexibility that the notebook provides, as it allows me to experiment with scripts. 

The solution offers the SageMaker Model Monitor, which helps monitor deployed models for performance issues like bias and drift. Also, the high scalability of SageMaker allows us not to worry about the underlying infrastructure, as it automatically adjusts based on demands.

The dashboard could be improved by including more features and providing more information about deployed models, their drift, performance, scaling, and customization options.

I have been working with Amazon SageMaker for about three years.

The stability of the solution is generally about an eight out of ten. Most instabilities arise from initial configuration errors rather than the infrastructure itself. Ensuring that the correct setup is chosen from the start minimizes these issues.

Amazon SageMaker is highly scalable, rated ten out of ten. It can scale up according to the demands detected by CloudWatch, providing a seamless experience without needing to manage the underlying infrastructure.

The customer service and support are rated as a five out of ten. The level of support depends on whether we are a premium AWS customer or not, with premium customers receiving better and more immediate support.

Neutral

The initial setup of SageMaker can be challenging for beginners, rated as a six, but easier for those with a background in machine learning, rated as a nine out of ten. Experience with machine learning is crucial for a straightforward setup. Without it, understanding the roles of different features can be a stumbling block.

Pricing is rated as a six, which is slightly more expensive compared to the budget yet adequate for the capabilities provided. On average, customers pay about $300,000 USD per month.

On a scale from one to ten, where ten is the best, I rate Amazon SageMaker as a nine. For new users evaluating SageMaker, it is important to remember that it takes some learning, however, the solution is straightforward and beneficial. There are no special prerequisites except having an account.

I use SageMaker to use a "bring-your-own-model" setup. For SageMaker AutoML, we're fine and happy with it. It is restricted because you can't move through multiple algorithms. It seems to work only with two. One of the things I am doing is prototyping, and it's proving quite difficult to get our model working how we want it to. It's proving complex with many moving parts, and the documentation is only partially helpful. SageMaker requires a lot of work to get it working.

I spent the last four months trying to get a prototype working and exploring to bring in a model while exploring alternate models and making prototypes work. We've stepped back to AutoML for now. We might be using EKS, so we bring our containers. Within the containers, we can work with what we need to work with.

The superb thing that SageMaker brings is that it wraps everything well. It's got the deployment, the whole framework. When you couple it with step functions, you can do some very powerful things. It manages deployment, you have model monitoring, and you have model quality checks. It's got a lot of end-to-end services one needs to get a full machine-learning pipeline running. While I say that I had a struggle and blame the product partially, I am also impressed with the ecosystem. I would still use it over and above other competing products, but I don't know the Google setup. I have worked very briefly with Azure, so I can't do a proper card-to-card comparison, but I do like the ecosystems AWS brings. If a client came along and asked me to set up a machine learning ecosystem, a full machine learning production deployment, I would use Sagemaker.

The solution is complex to use.

Some additional functionality would be for them to provide sample end-to-end card formation templates and try to unify the setup. At the moment, as you move from one set of documentation to the next, some of the documentation is for bringing your model, some of the documentation is for SDK, some of it's for API, some of it's for command lines, and some of it's for step functions. None of the documentation seems to be end-to-end. There are gaps in the documentation. It proves to require a lot of digging from the user to figure it out. I did get through the AWS machine learning specialty certification, but that proved to be a bit superficial. Though it covered a lot of ground, it didn't have the detail one would need for Sagemaker. I am self-taught in a lot of the stuff. I could dive deeper into some code and take time to get examples running. But I was consulting a startup, and they needed to move quickly.

I was hoping SageMaker would be easier to work with because I was expecting there would be examples we could repurpose that were more complete.

The new functionality I'd like to see is Amazon tuning attention to the documentation sets and the templates.

I've been using Amazon SageMaker for about two and a half years.

Stability is not a relevant metric anymore because SageMaker runs on its own underlying AWS serverless infrastructure, which is 100% reliable.

Folks better than me with more extensive resources and time have run and checked SageMaker ten times a second every second for 1,000 hours to see if they got a drop, but they haven't. It's serverless and bulletproof.

I rate the scalability a ten out of ten. Part of the problem is that AWS has limited the functionality of SageMaker in many ways to make it scalable. So it's scalability first and then functionality second.

The solution works well for medium-sized businesses and up. But even for small businesses, you can do some simple and quick elastic endpoints and get going quickly. The problem is the amount of work it takes for people to know what they're doing with Sagemaker, and those people are probably rare. I've been able to get things up and running in most cases in all sorts of AWS services, but I'm struggling. Small, medium, and large enterprises could use SageMaker with an automatic model, but it depends on the people's skills doing the deployment. A small business probably couldn't afford contractors, consultants, or data scientists. It's not about AWS. It's a problem with classic data science skills.

I rate the initial setup a three or two out of ten because it's very complex.

You don't pay for Sagemaker. You only pay for the compute instances in your storage. SageMaker is free.

I've had a little bit of a look at Azure, but I didn't get into the level of detail I did with Sagemaker. I have worked reasonably intentionally with DataRobot and H20. But SageMaker is a way bigger, way more capable platform. The AutoML is very simple, and it is much, much cheaper. The cost of SageMaker is nothing. By contrast, if you're using DataRobot, you'll pay $100,000 plus for a five-year license.

Anyone doing on-prem at the moment for anything but their core datasets or legacy systems that can't be moved is just paying useless money.

I rate Amazon SageMaker a seven out of ten. I'd recommend it to other users. It's worth syncing the time and effort into getting it running.

We use Amazon SageMaker for model deployment, hosting, and monitoring.

There is a lot of control in the solution over which terms you want to pick and choose. You don't have to pick the end-to-end machine learning operation solution. You can just choose deployment or training if you want, a benefit I saw in the solution.

You can leverage AWS's accelerated hardware to run your machine learning models, which is beneficial for improving a model's performance in terms of runtime, which is how long it takes to execute. Amazon SageMaker is an AWS product, and the company I work for already hosts all its services on AWS. Everything works well together if you're already on AWS.

Amazon SageMaker is expensive. It is more expensive than Databricks because it has a pay-as-you-go model with SageMaker.

The pricing of the solution is an issue.

In SageMaker, the monitoring does not support data captured in a protocol called protobuf since it only accepts JSON and CSV. We use protobuf to exchange messages. We have to write our own logic to serialize protobuf, which is more work, and it'd be better if SageMaker provided out-of-the-box support for that.

In SageMaker, monitoring could be improved by supporting more data types other than JSON and CSV. Amazon SageMaker can start with Protobuf since it is a popular messaging protocol.

I have been using Amazon SageMaker for six months. We are using the latest version of the solution. My company has a partnership with Amazon.

I can't comment on the solution's stability because it's still in production.

The solution is easy to scale.

We have B2C Customers for the product, which would include over two million monthly recurring users.

I have not contacted Amazon regarding the support.

The documentation and online community support have been sufficient for us so far.

There is nothing to install since it is all cloud-based.

Deployments are a matter of minutes, depending on what kind of tool you use. I use AWS CDK for deployment, and with CDK, if you know what you're doing, it takes 15 minutes.

The solution is deployed on a public cloud.

The number of people required for deployment depends on the company and how fast they want to get it done. I had once completed PoC and the implementation part, and it took me some time, but deploying it alone is not an end-to-end solution. The deployment process requires the expertise of data scientists to build the model and an engineer to deploy it. Deployment would involve a maximum of two individuals.

Technically, you shouldn't need anyone because it's AWS-managed services.

The solution's worth depends on the company's use cases. For us, the solution is valid because we already run on AWS.

There is no license required for the solution since you can use it on demand.

Amazon SageMaker is definitely not the best product out there. I recommend that one can quickly do prototyping on SageMaker. It is easy to take your workload to the AWS Cloud. Amazon SageMaker's setup is very fast, so you'll be able to validate all your hypotheses pretty fast.

Overall, I rate the solution a seven out of ten.

I am currently using SageMaker for a range of tasks including data cleaning, data visualization, exploratory data analysis, data labeling, training, and deploying models. I am also using it for machine learning projects.

Amazon SageMaker has accelerated our machine learning development, improved scalability, optimized resource use, and reduced costs, enabling us to deliver faster, more efficient, and scalable ML solutions.

SageMaker is a comprehensive platform where I can perform all machine learning activities. Specifically, the notebook feature is beneficial because it allows me to do everything from data cleaning to model training, dataset transformation, and data visualization on a single platform.

I had to create custom templates for labeling multi-data sets, such as text and images, which was time-consuming. It would be appreciated if SageMaker made it more adaptable for different types of datasets instead of just specific ones.

There have been no performance or stability issues with SageMaker.

SageMaker is scalable.

I have not used customer support services. However, I did receive notifications regarding resource usage, such as a restart notice during long computations.

Positive

I have worked with generative AI, LLM models, APIs from Google, GPT, and Llama.

I switched because Amazon sagemaker comprises of most activities I needed from other different solutions. 

The initial setup was very straightforward with a left-side panel aiding in easy navigation. It was quite simple and user-friendly.

If you are not on the free tier, SageMaker might be expensive, especially if you forget to shut down running applications. However, since I am using some free-tier services, cost efficiency is not a concern for me.

I have worked with other solutions such as generative AI models and APIs from other providers. I have used Jupyter notebook via Anaconda, VSCode and Google Collab for my day to day machine learning tasks.

I would recommend SageMaker because it serves as a one-stop solution where everything needed for machine learning can be done in a single platform, without looking for other platforms to perform individual tasks.

I'd rate the solution nine out of ten.

We use Amazon SageMaker for a specific project involving an airline company to analyze historical flight data. Initially, we created a proof of concept locally and then developed a data pipeline to enhance the flow for large data models. This project benefited from SageMaker's ability to handle large data with TensorFlow, leading to a more efficient MLOps process.

SageMaker has streamlined the process for us, particularly in handling TensorFlow and making data management auto-scalable. This has allowed for a more efficient process, especially when discussing with DevOps about MLOps capabilities.

The most important feature is the ease of controlling costs with pricing calculators, which is crucial due to our limited budget. The low-code MLOps aspect simplifies data science work and makes it accessible for engineers without a DevOps background. It's user-friendly for business teams as they can understand many aspects through the AWS interface.

While not specific to SageMaker, I've observed a trend where companies are more attracted to the marketing of Gemini and GPT, leading some to migrate their pipelines to these platforms. Amazon might need to emphasize its capabilities in generative models more effectively.

SageMaker has proven to be stable with only one issue in our history, which is impressive.

Before SageMaker, pipelines were created manually. Since using SageMaker, I've been impressed with its high scalability, rating it a ten out of ten.

We have used free support tickets, and the response time is normal, usually in one or two days.

Positive

The initial setup was not complex, taking us about one month to fully understand and set it up, with the actual setup time being around one to two weeks.

We managed the implementation with two people focusing on understanding and making additional tests.

Compared to other top cloud services like Azure and Google Cloud in Brazil, AWS pricing is competitive and merits a rating of five out of ten.

We are migrating some models to Azure to evaluate its GPT enterprise version.

It's important for new users to clearly define the testing process and understand what they aim to achieve. SageMaker facilitates a fast, secure, and scalable MLOps process.

I'd rate the solution nine out of ten.

In my projects, I work with Amazon SageMaker to do face recognition using Amazon SageMaker and Amazon Lex. The platform is used for integrated development and utilizes features like Amazon Cognition for analyzing images and videos, as well as comparing images.

Amazon SageMaker provides a structured workflow from data sourcing, data processing, and data labeling to model training and deployment. This end-to-end workflow simplifies tasks and avoids confusion with other platforms, enhancing our efficiency. Moreover, its performance is commendable, especially in terms of computing speed, saving time effectively.

SageMaker offers functionalities like Jupyter Notebooks for development, built-in algorithms, model tuning, and options to deploy models on managed infrastructure. These features simplify the end-to-end machine learning workflow, including data labeling, preparation, reprocessing, training, deployment, and monitoring.

The user interface (UI) and user experience (UX) of SageMaker and AWS, in general, need improvement as they are not intuitive and require substantial time to learn how to use specific services. 

Additionally, the platform struggles with tuning large models, which is a significant limitation.

I have been working with SageMaker for five or six months.

I haven't faced any performance or stability issues with SageMaker.

Adding additional resources or scaling up to meet demand is not as straightforward as I would like.

I have not had any experience interacting with customer support or technical support for SageMaker.

Positive

I have not used other AI development platforms like Azure or GCP in my current work. My use of SageMaker is based primarily on its integration into our existing workflows.

I can't remember the initial setup process clearly after three months. However, there was a learning curve involved when I began using SageMaker.

I am unsure about the size of the implementation team specific to the use of SageMaker, however, it was used by our team of ten people.

The pricing is based on usage, and I find it reasonable for what we use it for.

I suggest SageMaker for anyone looking to facilitate an end-to-end machine learning workflow, from preparing data to deploying models, due to its comprehensive feature set.

I'd rate the solution eight out of ten.

We use Amazon SageMaker primarily for training and deploying end-to-end models for our specific use cases. We take models from the interface and deploy them to the staging environment, ensuring they are monitored 24/7. This tool is essential for deploying models. 

The most tool's valuable feature, in my experience, is hyperparameter tuning. It allows us to test different parameters for the same model in parallel, which helps us quickly identify the configuration that yields the highest accuracy. This parallel computing capability saves us a lot of time. 

One area where Amazon SageMaker could improve is its pricing. The high costs can drive companies to explore other cloud options. Additionally, while generally good, the updates sometimes come with bugs, and the documentation could be much better. More examples and clearer guidance would be helpful.

I have been working with the product for six to seven months. 

The solution is a stable product.

My company has 300 to 400 users. The solution is scalable. 

We contacted AWS support, and we are happy with them. 

We are AWS partners and blindly go with AWS products. 

Regarding the initial installation, setup, and deployment, I would rate it as medium difficulty. Since it operates within the AWS ecosystem, you must follow specific rules and understand how AWS works. It can take around four to five months to fully deploy a model, understand its running and training processes, and get everything set up properly.

If you want to use Amazon SageMaker for the first time, I would advise completing one of the AWS certifications and reading the documentation thoroughly. Having someone experienced with the product to guide you can also be very helpful.

Despite its high price, the tool is continually evolving, and updates are frequent and relevant. However, due to its pricing and some issues, I would rate it a seven out of ten.