aws / aws/sagemaker-python-sdk
MLFlow E2E Example Notebook
- Vorherrschende Sprache
- Python
- Sterne
- 2.3k
- Forks
- 1.3k
- Ø Merge
- 1 T. 22 Std.
- Gemergte PRs (30 T.)
- 35
Beschreibung
**PR**: https://github.com/aws/sagemaker-python-sdk/pull/5514
**Describe the feature you'd like**
Add a new example notebook demonstrating the complete end-to-end workflow from training a PyTorch model to deploying it for inference on SageMaker, with MLflow 3.x tracking and model registry integration.
**How would this feature be used? Please describe.**
Users who want to leverage MLflow with SageMaker V3 SDK currently lack a comprehensive example showing the full workflow. This notebook would demonstrate:
1. Connecting to SageMaker MLflow tracking server
2. Training a PyTorch model with ModelTrainer while logging metrics/params to MLflow
3. Registering the trained model to MLflow Model Registry
4. Deploying directly from MLflow registry using ModelBuilder
5. Testing the deployed endpoint
Example workflow:
```
# Train with MLflow logging
model_trainer = ModelTrainer(training_image=..., source_code=...)
model_trainer.train()
# Deploy from MLflow registry
model_builder = ModelBuilder(
model_metadata={"MLFLOW_MODEL_PATH": "models:/my-model/1", ...}
)
model_builder.build()
model_builder.deploy()
```
**Describe alternatives you've considered**
Existing notebooks cover training or inference separately, but none show the integrated MLflow workflow end-to-end.
**Additional context**
Target location: v3-examples/ml-ops-examples/
Notebook name: v3-mlflow-train-inference-e2e-example.ipynb
Prerequisites: SageMaker MLflow App (tracking server ARN)
Beitragsleitfaden
Rechercherichtung
Beginne in v3-examples/ml-ops-examples/ und verwende die ARN-Voraussetzung für den SageMaker MLflow App-Tracking-Server. Erstelle v3-mlflow-train-inference-e2e-example.ipynb, das PyTorch-Training mit MLflow-Logging, die Modellregistrierung, die Bereitstellung über ModelBuilder und das Testen des Endpunkts abdeckt; als abgeschlossen gilt die Aufgabe, wenn der vollständige Workflow demonstriert wird.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- jupyter-notebook, python, pytorch
- Bereich
- cloud, documentation, machine-learning
- Issue-Typ
- Feature
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 25/100