With the AWS SageMaker integration, you can manage and monitor your SageMaker deployments in Deeploy.
Connect to SageMaker
The SageMaker integration is controlled on a license level. Admins can set up the SageMaker integration on the integrations page (Admin Panel -> Integrations) by using the 'Connect' button on the SageMaker card (Image 1).
Image 1: SageMaker card as seen on the integrations page
Enter the required information in the modal (Image 2):
- AWS Access Key ID & AWS Secret Access Key
We needs AWS credentials to access the necessary resources on your AWS account. To get your AWS credentials, follow these instructions. Create a role with the following minimal permissions:
- Default AWS region
We need the AWS region used for your AWS account for authentication, and to use as a default region for your SageMaker deployments. You can always specify a different region when creating a deployment (see also Image 3).
- SageMaker ARN
Specify the execution role you want to use for SageMaker Deployments, using the Amazon Resource Name (ARN) format. The default AWS execution role is "arn:aws:iam::<YOUR-ACCOUNT-ID>:role/SagemakerFullAccess".
Image 2: Modal for setting up the SageMaker integration
Start using SageMaker for Deployments
There are two ways you can start creating SageMaker Deployments in Deeploy, both are detailed below. For more information on how to create Deployments themselves, check out Creating SageMaker Deployments
1. Make SageMaker your default Deployment backend
The default Deployment backend is controlled on Workspace level. Workspace admins can set the default Deployment backend to SageMaker in the Workspace settings. All Deployments use the default Deployment backend, unless specified otherwise when creating a deployment.
2. Create a single SageMaker Deployment
The Deployment backend can be edited when creating a deployment. This means you can create a Deployment using SageMaker, when the default Deployment backend is set to KServe (and vice versa). To change the Deployment backend to SageMaker for a single Deployment, untoggle the 'Use default backend settings' toggle in the second step of the create flow ('Deployment'), and select SageMaker from the dropdown (Image 3).
Image 3: 'Use default backend settings' untoggled