Amazon SageMaker Reviews

We use the solution to extract financial information and contractual data from unstructured documents.

The product provides the ability to develop AI models relatively quickly. My team develops the models using the tool. We use AI quite extensively in our business. We use the tool for predictive analytics. It helps predict which trade might fail based on historical data. Automatic Model Tuning helps improve the productivity of the investment operation team. Typically, an analyst spends about 45% of their time collecting, organizing, and ingesting data. We were able to use the product to automate processes.

The solution requires a lot of data to train the model.

I have been using the solution for the past 12 months.

The tool’s stability is pretty high. I rate the stability a nine and a half or ten out of ten.

The scalability is very high. I rate the scalability a nine out of ten. We are a small team of AI analysts. We have half a dozen users.

The support is usually pretty responsive. The solution has a fair bit of content online. We haven't had any support challenges.

Positive

We were using Azure’s tool before. We switched to Amazon SageMaker because it allows us to sell it to larger institutional clients. AWS is more prevalent in the broader institutional segment.

The initial setup is relatively straightforward. The same team developing the models deploys and tests the solution. The tool requires a bit of ongoing maintenance. It is relatively easy to do.

The product is expensive. I rate the pricing a five or six out of ten.

We are partners and resellers. Overall, I rate the product a nine out of ten.

I am currently working with AWS services like SageMaker, S3, EC2, VPC, load balancing, auto scaling, and RDS. SageMaker is used primarily for AI projects to build, train, and deploy AI models from scratch.

SageMaker supports building, training, and deploying AI models from scratch, which is crucial for my ML project. It provides lifecycle configurations, similar to EC2's user data, for running scripts on instances. It also offers VPC features to isolate SageMaker instances when needed, which is a valuable use case.

The entry point can be a bit difficult. Having all documentation easily accessible on the front page of SageMaker would be a great improvement.

I have been working with SageMaker for about one week due to a project related to AI.

I have not encountered any stability issues with SageMaker so far.

Scaling SageMaker has not been an issue. If required, I can increase the instance size to a higher tier as needed.

I haven't needed to contact AWS technical support for this project.

Positive

When I first started working with SageMaker, I was unfamiliar with it. I consulted AWS articles and searched online to understand how SageMaker works.

I was responsible for deploying SageMaker for my client and configuring notebook instances with VPC and subnets.

Before deploying SageMaker, I reviewed the pricing, especially for notebook instances. The cost for small to medium instances is not very high.

I recommend SageMaker for ML projects if you need to build models from scratch. If you do not want to maintain the instances, consider using Datablock instances. On a scale of one to ten, I would rate SageMaker a nine.

The primary use case for Amazon SageMaker is leveraging its compute power, particularly for tasks like securing LMM notebooks using node instances. Additionally, its GPU capabilities are valuable for executing large language models. Users can create endpoints and access them from anywhere as needed.

We've had experience with unique ML projects using SageMaker. For example, we're developing a platform similar to ChatGPT that requires models. We utilize Amazon SageMaker to create endpoints for these models, making accessing them convenient as needed.

The main function I prefer in Amazon SageMaker is the ability to create endpoints for large models. I haven't explored features like Studio Lab yet, but I've found the tutorials very helpful. The platform is user-friendly, with documentation attached to everything, making it easy to navigate and learn. Overall, I especially like the Studio Lab feature.

In the Studio Lab, tutorials provide direct snippets for tasks like connecting to S3 from Amazon SageMaker. These standard snippets make implementation straightforward and simplify the development process for me.

In my opinion, one improvement for Amazon SageMaker would be to offer serverless GPUs. Currently, we incur costs on an hourly basis. It would be beneficial if the tool could provide pay-as-you-go pricing based on endpoints. 

In the three months I've been using it, I've noticed that higher GPU instances can be quite costly. To mitigate this cost impact, serverless GPUs would be beneficial.

I have been working with the product for three months. 

I rate the solution's stability a nine out of ten. 

I rate the tool's scalability an eight out of ten. No issues with scalability as long as we ensure we have the necessary quotas in place before implementing a scalable process. I needed to request quota increases for certain services beforehand, and once those were provided, I could adjust the main and max nodes accordingly based on our planned requirements. My company has 25 users. 

We can schedule a direct call with the support team. 

Amazon SageMaker's Studio Lab feature differentiates it from products like Azure ML Studio. With Studio Lab, I can directly interact with the environment, making navigating and accessing documentation easier. In contrast, finding documentation and navigating Azure ML Studio was challenging.

However, we also use Azure for the Azure OpenEdge service, which operates on a pay-per-minute token basis. This payment model is not available in Amazon SageMaker. 

The initial setup and deployment process for Amazon SageMaker is straightforward. The only complexity I encountered was gaining access to the needed resources, which relied on coordination with the DevOps team. Once I had access sorted out, implementing my ideas for large language models and other models was comfortable. 

The tool's pricing is reasonable. 

I rate the overall solution an eight out of ten. 

I use Amazon SageMaker to develop modules with data stored in AWS, extracted from SAP. After building the modules, I deploy them to assess their performance and efficiency.

Amazon SageMaker has significantly enhanced our organization by consistently introducing new features like model tracking and recently integrating with MLflow. This integration provides me with increased flexibility for experimentation, making it easier to explore and implement innovative solutions.

The most beneficial feature for streamlining my machine learning workflows in Amazon SageMaker is MLflow. It allows me to experiment more effectively before finalizing decisions which enhances the progress of my machine learning projects.

Amazon SageMaker's integration with Jupyter Notebooks has significantly improved my data exploration and experimentation process. The built-in IDE is excellent and has been useful from the beginning, providing a seamless and effective platform for my work.

The most valuable feature of Amazon SageMaker for me is the model deployment service. Serving the model is crucial because it seamlessly scales with the operation of the model, providing efficient infrastructure that adapts to the scaling needs, and ensuring optimal performance.

Amazon SageMaker could improve in the area of hyperparameter tuning by offering more automated suggestions and tips during the tuning process. Having integrated intelligence to suggest hyperparameters would be beneficial for optimization.

I have been working with Amazon SageMaker for two years.

I would rate the stability as a six out of ten since there is room for improvement in the user experience to enhance both scalability and stability.

I would rate the scalability of Amazon SageMaker as a seven out of ten. We have about ten users of it at our company.

The tech support for Amazon SageMaker is not good, especially for new users. There is a need to scale and improve support services to provide better assistance for users, particularly those who are less experienced with the platform. I would rate the support as a five out of ten.

Neutral

I would rate the easiness of the initial setup as a six out of ten. The process of using Amazon SageMaker has some challenges, mainly due to the complexity of multiple components. Streamlining the deployment process with better scripting support would be beneficial, addressing the difficulties associated with managing various moving parts in the platform.

The deployment process in Amazon SageMaker is smooth once the initial setup is done. Integrating with other AWS services like RDS is a key aspect, requiring attention to connections and overall integration for a successful deployment.

I would rate the costliness of the solution as a six out of ten. It could be a bit cheaper.

I evaluated other options like ML Studio and a few others but chose Amazon SageMaker because of my familiarity with their services and features.

I use Amazon SageMaker in our production environment for making predictions in batches, ensuring efficient and scalable processing of large datasets.

Overall, I would rate Amazon SageMaker as a six out of ten.

The primary use cases for Amazon SageMaker are for EDA processing, ML model building, setting up MLOps, predictive analysis, customer churn models, fraud detection, image and video analysis, as well as NLP projects. It is a versatile tool in the machine-learning landscape.

The most valuable features in Amazon SageMaker are its AutoML, feature store, and automated hyperparameter tuning capabilities. These features allow for generating high-quality models without needing extensive coding knowledge, making it accessible for non-experts. SageMaker helps in end-to-end machine learning, incorporating data preparation, model deployment, and continuous monitoring.

Improvements are needed in terms of complexity, data security, and access policy integration in Amazon SageMaker. It is considered complex to integrate these aspects, and adjustments need to be made in multiple places, which should be more user-friendly. A centralized interface for managing these configurations is desired.

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

Amazon SageMaker's stability depends on how well-configured the entire setup is. Due to the interconnected dependencies within the system, the learning curve may be steep for new users. However, with proper configuration, the overall stability is adequate.

Amazon SageMaker offers a high level of scalability. It allows dynamic resource allocation and supports large datasets through various features like multi-model endpoints and flexible instance configuration, scaling up or down according to requirements.

Technical support for Amazon SageMaker involves communication through web chats or telephone based on the support agreement.

Positive

In AWS, we used to build the whole pipeline model by ourselves, component by component. With Amazon SageMaker, costs have been optimized as it includes pre-configured components that reduce overall expenses.

The initial setup of Amazon SageMaker can be achieved quickly if the default configuration is used. However, setting it up more customizable, such as for specific requirements, can make the process time-consuming, earning an eight out of ten in terms of ease.

A single knowledgeable person with expertise in ML and cloud can handle the deployment and maintenance of Amazon SageMaker.

We have seen a significant reduction in costs using Amazon SageMaker. Building any ML lifecycle benefits from SageMaker's pre-configured components, which bring down the overall cost compared to setting up all components separately.

While Amazon SageMaker is expensive compared to other cloud vendors, certain cost optimizations can be made with proper setup and configuration knowledge. Greater visibility from AWS regarding cost-impacting configurations would be beneficial.

No other solutions were evaluated outside of AWS, as we were setting everything up within AWS before opting to use Amazon SageMaker.

I rate SageMaker eight out of ten. 

New users should conduct a pilot or proof of concept with Amazon SageMaker to see if it aligns with their business use cases. Evaluate and understand the integration with other AWS services and ensure the team has adequate knowledge to handle monitoring, model performance, and managing costs efficiently. Engaging with the community to remain updated on any misconfigurations is also advisable.

I use Amazon SageMaker for data preparation and machine learning. We create an automated pipeline to ensure datasets are prepared every day, conduct model training, and monitor and optimize models along with making predictions.

It helps us monitor our models on a daily basis, allowing us to check the performance with new data, compare different models, and replace or optimize non-performing ones. It also assists with feature lineage, enabling us to track features throughout the pipeline.

The feature I found most valuable is the data catalog, as it assists with the lineage of data through the preparation pipeline.

The platform could be more accessible to users with basic coding skills, making it more intuitive and easier for beginners to use comfortably.

I have worked with SageMaker for three or four years.

There have been incidents of downtimes. That said, I am not aware of the frequency as I am not in charge of monitoring. These occurrences cause some consequences, but they rarely impact daily operations critically.

SageMaker is highly scalable, with a rating of ten out of ten, as it effectively handles a large volume of daily data, helping with data preparation and prediction integration.

The technical support team is very helpful, with a rating of nine out of ten. They assist us well with resolving service issues and provide valuable advice.

Positive

The initial setup and deployment were handled by another team within the organization.

I'd rate the solution ten out of ten.

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.

The primary use case of Amazon SageMaker is for training a small AI module for learning purposes. It was used for the training of a small machine learning model.

I appreciate the ease of use in Amazon SageMaker. I have not explored many features, as I am not deeply involved yet, but I aim to enhance my skills in the future. 

Based on my existing experience, it was straightforward to train a small machine-learning model. I initially used AWS Skill Builder for guidance, making it manageable without encountering challenges. 

In scalability, I found it highly scalable, having used the Jupyter notebook and other tools. By scaling the model, I've had a positive experience.

I would recommend having more walkthrough videos and articles beyond AWS Skill Builder. There should be additional articles within the services.

In terms of stability, I have not experienced any breakdowns. Although I have heard reports that it might break, I have personally never faced any issues with the stability of Amazon SageMaker.

I found that Amazon SageMaker is highly scalable. I used the Jupyter notebook and explored other available tools, which were useful depending on what I utilized. I plan to enhance my model in the future, which will allow me to share more about scalability once I fully scale the models.

The support team of Amazon is excellent. I found them to be very good.

Positive

I have not used anything else in cloud computing. Amazon SageMaker was my entry-level experience in cloud computing.

I would give Amazon SageMaker a solid score of eight out of ten since I have not used much of its services. 

Based on the small model I trained, I would recommend it to others. I have already recommended it to some colleagues, batchmates, and fellows. My advice to newcomers would be to look for walkthrough videos and articles to aid in their learning.