Guidance for Bringing Your Own Machine Learning Models into Amazon SageMaker Canvas
Overview
This Guidance shows how you can bring your own machine learning (ML) models into Amazon SageMaker Canvas and remove the need to manually change your code that is often required when building or moving ML models in new environments. In this Guidance, we showcase three patterns for how your teams can use ML models with SageMaker Canvas. One, you can register ML models in the SageMaker model registry, which is a metadata store for ML models. Two, you can directly share models built using Amazon SageMaker Autopilot. Three, you can use Amazon SageMaker Jumpstart and import the ML models into SageMaker Canvas. Business analysts can then analyze and generate predictions from any model in Canvas without writing a single line of code.
How it works
This architecture diagram shows how business analysts can use Amazon SageMaker Canvas to load machine learning models, which can be trained anywhere, and generate predictions in the UI. All without writing a single line of code.
Well-Architected Pillars
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages