
## Crawl AWS SageMaker Unified Studio

URL: https://docs.atlan.com/apps/connectors/data-governance/aws-sagemaker-unified-studio/how-tos/crawl-aws-sagemaker-unified-studio

> Configure and run the SMUS Catalog crawler to extract assets, metadata, and lineage from SMUS and catalog and enrich them in Atlan.

Configure and run the SMUS Catalog crawler to extract assets, metadata, and lineage from SMUS and catalog and enrich them in Atlan.

## Prerequisites

Before you begin, make sure you have:

* [Set up AWS SageMaker Unified Studio authentication](https://docs.atlan.com/llms/connectors/aws-sagemaker-unified-studio/set-up-aws-sagemaker-unified-studio/llms.txt)
* Admin or connection admin privileges in Atlan
* AWS credentials (Access Key ID and Secret Access Key or IAM Role ARN)
* AWS region

## Create crawler workflow

To crawl metadata from AWS SageMaker Unified Studio, review the [order of operations](https://docs.atlan.com/llms/catalog/connector-capabilities/order-workflows/llms.txt) and then complete the following steps.

1. In your Atlan workspace, click **Connectors** in the left sidebar.
 * If you are using the **Old UI (Classic)**, click **New Workflow** in the top navigation.

2. Click **Marketplace**.

3. Search for **AWS SageMaker Unified Studio**, select it, and click **Install**.

4. Once installation completes, click **Setup Workflow** on the same tile.

---

### Configure authentication

Configure how Atlan authenticates with your AWS account to access SageMaker Unified Studio. Choose the authentication method that matches your security requirements.

### IAM Role

1. Enter your role details:
 * **AWS Role ARN**: Enter your IAM Role ARN for cross-account access (for example, `arn:aws:iam::123456789012:role/role-name`). This is the SMUS IAM Role created by deploying the CloudFormation template earlier.
 * **External ID**: Enter an external ID for additional security
 * **Atlan API Token**: Enter your [Atlan API token](https://docs.atlan.com/llms/platform/get-started/api-access/llms.txt)
 * **Region**: Enter your primary SageMaker Catalog region (for example, `us-east-1`)
2. Click **Test Authentication** to verify your AWS credentials work correctly.

3. Once successful, click **Next**.

### IAM User

1. Enter your user credentials:
 * **AWS Access Key**: Enter your AWS access key ID
 * **AWS Secret Key**: Enter your AWS secret access key
 * **Atlan API Token**: Enter your [Atlan API token](https://docs.atlan.com/llms/platform/get-started/api-access/llms.txt)
 * **Region**: Enter your primary SageMaker Catalog region (for example, `us-east-1`)
2. Click **Test Authentication** to verify your AWS credentials work correctly.

3. Once successful, click **Next**.

### Configure connection

1. Provide a **Connection Name** that represents your source environment. For example, you might want to use values like `production`, `development`, or `analytics`.

2. To change the users able to manage this connection, change the users or groups listed under **Connection Admins**. If you don't specify any user or group, nobody can manage the connection, including admins.

3. Click **Next** to proceed.

### Configure crawler

1. To filter which projects are crawled, use the following optional fields:
 * **Include AWS SageMaker Unified Studio Projects**: Select specific projects to include in the crawl. Leave empty to include all projects.
 * **Exclude AWS SageMaker Unified Studio Projects**: Select specific projects to exclude from the crawl.
2. For **Enable Reverse Sync**, choose whether to sync metadata changes from Atlan back to SMUS:
 * **Yes**: Atlan syncs supported metadata changes back to SMUS. For details, see [Bidirectional metadata sync](https://docs.atlan.com/llms/connectors/aws-sagemaker-unified-studio/bidirectional-metadata-sync/llms.txt).
 * **No**: Atlan doesn't sync changes back to SMUS.
3. For **Enrich Business Graph**, choose whether to ingest glossaries from SMUS:
 * **Yes**: Atlan ingests glossaries from SMUS and enriches them in Atlan.
 * **No**: Atlan skips glossary ingestion.
4. If you selected **Yes** for **Enrich Business Graph**, select the **Business Graph** in Atlan you want to enrich with glossaries from SMUS.

5. Click **Next** to proceed.

### Run crawler

1. To check for any permissions or configuration issues before running the crawler, click **Preflight checks**. For details about the checks performed, see [Preflight checks for Amazon SageMaker Unified Studio](https://docs.atlan.com/llms/connectors/aws-sagemaker-unified-studio/preflight-checks-for-aws-sagemaker-unified-studio/llms.txt).

2. You can either:
 * To run the crawler once immediately, click **Run**.
 * To schedule the crawler to run hourly, daily, weekly, or monthly, click **Schedule Run**.

Once the crawler has completed running, run the [domain-assets linking script](https://docs.atlan.com/llms/connectors/aws-sagemaker-unified-studio/domain-assets-linking/llms.txt) to link your SMUS assets to the corresponding Data Domains in Atlan.

After running the script, you can now see the assets in Atlan's asset page! 🎉

## See also

* [Preflight checks for Amazon SageMaker Unified Studio](https://docs.atlan.com/llms/connectors/aws-sagemaker-unified-studio/preflight-checks-for-aws-sagemaker-unified-studio/llms.txt): Technical validations you can run before crawling
* [What does Atlan crawl from SMUS Catalog?](https://docs.atlan.com/llms/connectors/aws-sagemaker-unified-studio/what-does-atlan-crawl-from-smus-catalog/llms.txt): Learn what assets and metadata Atlan extracts from SageMaker Catalog

---
