|
1 | 1 | # Amazon SageMaker AI Deployment |
2 | 2 |
|
3 | 3 | Use the TensorFlow DLC for training jobs launched via the SageMaker Python SDK or `boto3`. The images bundle the `sagemaker-tensorflow-training` |
4 | | -toolkit, OpenMPI for multi-node coordination, and SageMaker-specific Python libraries (`mlflow`, `smclarify`, `pandas`, `seaborn`, `s3fs`, |
5 | | -etc.). |
| 4 | +toolkit, OpenMPI for multi-node coordination, and SageMaker-specific Python libraries (`mlflow`, `smclarify`, `pandas`, `seaborn`, `s3fs`, etc.). |
6 | 5 |
|
7 | 6 | The TensorFlow 2.21 DLC is a **SageMaker-only** release — there is no EC2 or EKS variant of this image. Point your estimators, processors, and |
8 | 7 | training jobs at the SageMaker image URIs shown below. |
@@ -108,23 +107,22 @@ processor = FrameworkProcessor( |
108 | 107 | SageMaker provisions EFA on the instance types that support it (e.g., `ml.p5.48xlarge`, `ml.p4d.24xlarge`). The GPU image ships with EFA 1.49.0 and |
109 | 108 | OpenMPI 4.1.8 pre-installed — no extra plumbing in your training script. |
110 | 109 |
|
111 | | -Multi-node peer discovery is handled by the `sagemaker_tensorflow_container` training toolkit, which parses |
112 | | -`/opt/ml/input/config/resourceconfig.json` at container start to enumerate hosts, current host rank, and network interface. Peers are addressed |
113 | | -by the SageMaker-assigned hostnames (e.g., `algo-1`, `algo-2`) that resolve inside the training cluster — your script does not need to know about |
114 | | -this. |
| 110 | +Multi-node peer discovery is handled by the `sagemaker_tensorflow_container` training toolkit, which parses `/opt/ml/input/config/resourceconfig.json` |
| 111 | +at container start to enumerate hosts, current host rank, and network interface. Peers are addressed by the SageMaker-assigned hostnames (e.g., |
| 112 | +`algo-1`, `algo-2`) that resolve inside the training cluster — your script does not need to know about this. |
115 | 113 |
|
116 | 114 | ## Container Layout |
117 | 115 |
|
118 | | -| Path | Purpose | |
119 | | -| ------------------------------------ | ---------------------------------------------------------------------------------------------- | |
120 | | -| `/opt/ml/input/data/<channel_name>/` | Training data SageMaker mounts from S3 (one subdir per channel) | |
121 | | -| `/opt/ml/model/` | Write your final model artifacts here — SageMaker uploads to `OutputDataConfig.s3_output_path` | |
122 | | -| `/opt/ml/output/` | Auxiliary outputs (logs, checkpoints) | |
123 | | -| `/opt/ml/code/` | Your training source dir (populated from the SDK's `source_dir`) | |
124 | | -| `/opt/venv/` | Python venv with TensorFlow + DLC libraries | |
| 116 | +| Path | Purpose | |
| 117 | +| --- | --- | |
| 118 | +| `/opt/ml/input/data/<channel_name>/` | Training data SageMaker mounts from S3 (one subdir per channel) | |
| 119 | +| `/opt/ml/model/` | Write your final model artifacts here — SageMaker uploads to `OutputDataConfig.s3_output_path` | |
| 120 | +| `/opt/ml/output/` | Auxiliary outputs (logs, checkpoints) | |
| 121 | +| `/opt/ml/code/` | Your training source dir (populated from the SDK's `source_dir`) | |
| 122 | +| `/opt/venv/` | Python venv with TensorFlow + DLC libraries | |
125 | 123 |
|
126 | 124 | ## Notes |
127 | 125 |
|
128 | | -- The image sets `SAGEMAKER_TRAINING_MODULE=sagemaker_tensorflow_container.training:main` — this is the entry-point the SageMaker |
129 | | - training toolkit invokes at container start, which in turn launches your `entry_point` script. |
| 126 | +- The image sets `SAGEMAKER_TRAINING_MODULE=sagemaker_tensorflow_container.training:main` — this is the entry-point the SageMaker training toolkit |
| 127 | + invokes at container start, which in turn launches your `entry_point` script. |
130 | 128 | - For a baseline driver/AMI compatible with these CUDA 12.9 images, request the latest SageMaker training AMI when launching jobs. |
0 commit comments