Configure AWS SageMaker

With the AWS SageMaker integration, you can manage, monitor, and explain your SageMaker deployments in Deeploy.

Connect SageMaker

The SageMaker integration is controlled on team level. Admins can set up the integration on the Integrations page, which is part of the Admin panel. Click Connect on the SageMaker card to set up the integration.

The following information is required:

• AWS access key ID & AWS secret access key Deeploy needs your AWS credentials to access the necessary resources on your AWS account. To get your AWS credentials, follow the AWS instructions. Create a role with the following minimal permissions:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "sagemaker:CreateEndpoint",
        "sagemaker:ListEndpoints",
        "sagemaker:DescribeEndpoint",
        "sagemaker:DeleteEndpoint",
        "sagemaker:UpdateEndpoint",
        "sagemaker:CreateEndpointConfig",
        "sagemaker:ListEndpointConfigs",
        "sagemaker:DescribeEndpointConfig",
        "sagemaker:DeleteEndpointConfig",
        "sagemaker:CreateModel",
        "sagemaker:ListModels",
        "sagemaker:DescribeModel",
        "sagemaker:DeleteModel"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "iam:PassRole"
      ],
      "Resource": "arn:aws:iam::*:role/SagemakerFullAccess"
    }
  ]
}

• Default AWS region Deeploy needs a default region to serve as the authentication region and default region for your SageMaker Deployments. However, you also have the flexibility to specify a different region when creating a Deployment.

• SageMaker Amazon Resource Name (ARN) Specify the execution role you want to use for SageMaker Deployments, using the ARN format. The default AWS execution role is arn:aws:iam::<YOUR-ACCOUNT-ID>:role/SagemakerFullAccess.

Get started with SageMaker for Deployments

You can get started with SageMaker Deployments by either making SageMaker your default Deployment backend, or creating single SageMaker Deployments. Both options are detailed in this section.

A guide to creating Deployments with SageMaker as a Deployment backend is available in Creating SageMaker Deployments.

SageMaker as your default Deployment backend

The default Deployment backend is controlled on a Workspace level. Workspace admins can change the default Deployment backend to SageMaker in the Workspace settings. All Deployments use the default Deployment backend, unless specified otherwise when creating a Deployment.

Create a single SageMaker Deployment

It's possible to create a Deployment using SageMaker, when the default Deployment backend is set to KServe or Azure Machine Learning (and vice versa). To change the Deployment backend for a single Deployment, untoggle the Use default backend settings toggle in the Deployment step when creating your Deployment, and choose SageMaker as your backend.