Skip to main content

Preflight checks for Amazon SageMaker Unified Studio

Before running the Amazon SageMaker Unified Studio crawler, you can run preflight checks to perform the necessary technical validations.

The following preflight checks are performed:

Authentication check​

This check verifies that the provided AWS credentials are valid and that the SageMaker Unified Studio (DataZone) APIs can be accessed.

The connector attempts to authenticate using the AWS SDK and confirms that the token/session is valid.

✅ SageMaker Unified Studio authentication successful

❌ Authentication failed: <error-message>

Client initialization check​

This check ensures that the SageMaker Unified Studio (DataZone) client can be successfully initialized using the provided AWS configuration (region, credentials, etc.).

✅ SageMaker Unified Studio client initialized successfully

❌ Failed to initialize SageMaker Unified Studio client: <error-message>

Domain access check​

This check verifies access to SageMaker Unified Studio domains by invoking the DataZone list_domains() API.

The connector attempts to retrieve the list of domains associated with the AWS account to verify the credentials have sufficient permissions.

✅ Access to <n> SageMaker Unified Studio domain(s) verified

❌ SageMaker Unified Studio domain access failed: <error-message>

Project access check​

This check validates that the connector can enumerate projects within each available domain by calling the DataZone list_projects() API.

The connector iterates through available domains and verifies that project metadata can be retrieved.

✅ Successfully verified project access across <n> domain(s). Found <m> total project(s) in <k> domain(s)

❌ Project access failed: <error-message>

Asset search check​

This check confirms that the credentials have permission to perform asset searches across SageMaker Unified Studio projects by invoking the DataZone search() API.

The connector performs a scoped asset search to validate:

  • Returned results are consistent with the available domains and projects
  • Permissions to read asset metadata

✅ Successfully tested asset search across <n> project(s) (<x> skipped). Found <y> asset(s) in <z> project(s)

❌ Asset search failed: <error-message>

See also​