mlflow/skills

sagemaker-mlflow

Connect to SageMaker Managed MLflow (mlflow-app or mlflow-tracking-server ARN) as an MLflow backend, then hand off to the other MLflow skills. Triggers on a…

Trending #6881 First seen Jul 10, 2026

Installation

$ npx skills add https://github.com/mlflow/skills
Feature your product here Skill page unit · reach builders installing agent skills View pricing →

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from mlflow/skills · top by installs.

npx skills add https://github.com/mlflow/skills

Browse all from mlflow/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 75
License LICENSE
Default branch main
Open issues 2
Status Active

History

  1. First seen on skills.sh
  2. First recorded snapshot · 154 installs

SKILL.md

Connect to SageMaker MLflow

Establishes the connection to SageMaker Managed MLflow (the sagemaker-mlflow plugin + an ARN tracking URI + AWS credentials), then hands off to the requested MLflow skill (instrumenting-with-mlflow-tracing, agent-evaluation, retrieving-mlflow-traces, querying-mlflow-metrics, etc.), which inherit the connection via MLFLOWTRACKINGURI.

Requires Python >= 3.10 (mlflow >= 3.8). Validate and report the fix — never auto-install the plugin or acquire credentials (mirrors the repo's Databricks pattern).

Step 1: Preconditions

  • python --version -> must be 3.10+. If older, STOP and tell the user.
  • Confirm AWS credentials resolve (env vars, aws configure / SSO, or an IAM role). If

they error (ExpiredToken / no creds), STOP and ask the user to configure them. (scripts/verify_connection.py also checks this, via boto3.)

Step 2: Install the plugin

pip install sagemaker-mlflow

Required even if MLFLOWTRACKINGURI is already an ARN — without it, mlflow.settrackinguri() fails with UnsupportedModelRegistryStoreURIException.

Step 3: Select the resource ARN

  • If the user already provided an ARN (or MLFLOWTRACKINGURI is set to

arn:aws:sagemaker:...), use it as-is.

  • Otherwise, discover it in the user's region:

``bash python scripts/discover_arns.py ` If exactly one is returned, use it; if several, list name/status/ARN and ask the user which to use. Both mlflow-app and mlflow-tracking-server` ARNs work; the ARN is also shown on the resource's detail page in the SageMaker Studio console.

Then export it (the ARN is region-bound — a cross-region ARN will not authenticate):

export MLFLOW_TRACKING_URI="<arn>"    # mlflow-app/<id> or mlflow-tracking-server/<name>
export AWS_DEFAULT_REGION="<region>"  # AWS credentials resolved via the default chain (SigV4)

Step 4: Verify

python scripts/verify_connection.py "$MLFLOW_TRACKING_URI"

Checks all three prerequisites (plugin / credentials / ARN connectivity) and exits non-zero with a remediation hint on the first failure. Do not proceed until it passes.

After the connection verifies, hand off to the requested MLflow skill — it inherits the connected environment via MLFLOWTRACKINGURI.

Troubleshooting

  • UnsupportedModelRegistryStoreURIException — the sagemaker-mlflow plugin is not

installed; pip install sagemaker-mlflow, then re-run scripts/verify_connection.py.

  • AccessDenied / 403 — credentials are missing/expired, or the principal lacks MLflow

permissions on the ARN. Check that credentials resolve, grant sagemaker-mlflow / sagemaker permissions, and confirm the ARN region matches AWSDEFAULTREGION.