> For the complete documentation index, see [llms.txt](https://docs.datasaur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasaur.ai/llm-projects/models/amazon-sagemaker-jumpstart.md).

# Amazon SageMaker JumpStart

## Overview

Amazon SageMaker JumpStart integration in LLM Labs lets you connect and manage your own models and deployed new ones in Datasaur, making them available for evaluation and deployment within LLM Labs.

## Setup

### Connect to Amazon SageMaker Jumpstart

1. Select **Amazon SageMaker JumpStart.**

   <figure><img src="/files/nOG9tl14VjkPnxbmYUsO" alt=""><figcaption></figcaption></figure>
2. An External ID is generated each time the dialog is opened. This ID will be used later when creating the role ARN. To avoid regenerating a new External ID, **do not close the dialog during setup**. Otherwise, you'll need to create the Role ARN with a different External ID.
3. You can start by selecting the **Region** attribute. We'll get back to this window later. Let's leave it for now.

   <figure><img src="/files/tsjA5sA1qB3FybC0U72H" alt=""><figcaption></figcaption></figure>

### Create a role ARN

Create a role which will be assumed by Datasaur to access your Amazon SageMaker Jumpstart.

1. Open the [IAM console](https://console.aws.amazon.com/iam/).
2. Go to **Roles** and then click **Create role**.
3. Choose **Custom trust policy** in the trusted entity type section.

<figure><img src="/files/r6liPaUjhoYEGDuNd5QB" alt=""><figcaption><p>Custom Trust Policy</p></figcaption></figure>

4. Paste the following configurations in custom trust policy. Don't forget to replace the **ExternalID.** After that, click **Next**.

```
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "AWS": "682361690817"
            },
            "Action": "sts:AssumeRole",
            "Condition": {
                "StringEquals": {
                    "sts:ExternalId": "<externalID>"
                }
            }
        },
        {
            "Effect": "Allow",
            "Principal": {
                "Service": "sagemaker.amazonaws.com"
            },
            "Action": "sts:AssumeRole"
        }
    ]
}
```

5. In the **Add permissions** section, select the **AmazonSageMakerFullAccess** policy. Then, click **Next**.

<figure><img src="/files/QiwpzDvbynlvOOfHJxS1" alt=""><figcaption></figcaption></figure>

6. Enter a **Role name** and a **Description** (optional).
7. Click **Create role**.
8. After that, back on the **Roles** page, click your newly created role.
9. Copy the **Role ARN** from the page and paste it in the **Amazon SageMaker Jumpstart** dialog in Datasaur. Then, click **Add Credentials** to connect.

## **Disconnect**

1. Click **Manage providers**, then click **View details** on Amazon SageMaker JumpStart provider.

   <figure><img src="/files/NssArMip664VstErLgeZ" alt=""><figcaption></figcaption></figure>
2. In the dialog that opens, click **Disconnect** at the bottom left.

   <figure><img src="/files/Kdld3IV5EdjTrnHuY2fe" alt=""><figcaption></figcaption></figure>
3. All Amazon SageMaker JumpStart models linked to that credentials will be removed from the workspace.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.datasaur.ai/llm-projects/models/amazon-sagemaker-jumpstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
