Skip to main content
Sagemaker allows users to host any ML model on their own AWS infrastructure. With Obiguard you can manage/restrict access, log requests, and more.
Provider Slug. sagemaker

Obiguard SDK Integration with AWS Sagemaker

1. Install the Obiguard SDK

Add the Obiguard SDK to your application to interact with Sagemaker’s API through Obiguard’s gateway.

2. Initialize Obiguard with a Virtual Key

There are multiple ways to integrate Sagemaker with Obiguard. You can use your AWS credentials, or use an assumed role. In this example we will create a virtual key and use it to interact with Sagemaker. This helps you restrict access (specific models, few endpoints, etc).
Here’s how to find your AWS credentials:

AWS Access Key


Use your AWS Secret Access Key, AWS Access Key Id, and AWS Region to create your Virtual key.

Integration Guide

AWS Assumed Role


Take your AWS Assumed Role ARN and AWS Region to create the virtual key.


Create a virtual key in the Obiguard dashboard in the virtual keys section. You can select sagemaker as the provider, and fill in deployment details. Initialize the Obiguard SDK with the virtual key. (If you are using the REST API, skip to next step)

3. Invoke the Sagemaker model

Making Requests without Virtual Keys

If you do not want to add your AWS details to Obiguard vault, you can also directly pass them while instantiating the Obiguard client. These are the supported headers/parameters for Sagemaker (Not required if you’re using a virtual key):

Example

Next Steps

The complete list of features supported in the SDK are available on the link below.

SDK