You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: advanced_functionality/scikit_bring_your_own/container/ReadMe.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This example shows how to package an algorithm for use with SageMaker. We have c
4
4
5
5
SageMaker supports two execution modes: _training_ where the algorithm uses input data to train a new model and _serving_ where the algorithm accepts HTTP requests and uses the previously trained model to do an inference (also called "scoring", "prediction", or "transformation").
6
6
7
-
The algorithm that we have built here supports both training and scoring in IM with the same container image. It is perfectly reasonable to build an algorithm that supports only training _or_ scoring as well as to build an algorithm that has separate container images for training and scoring.v
7
+
The algorithm that we have built here supports both training and scoring in SageMaker with the same container image. It is perfectly reasonable to build an algorithm that supports only training _or_ scoring as well as to build an algorithm that has separate container images for training and scoring.v
8
8
9
9
In order to build a production grade inference server into the container, we use the following stack to make the implementer's job simple:
10
10
@@ -18,7 +18,7 @@ The components are as follows:
18
18
19
19
*__Dockerfile__: The _Dockerfile_ describes how the image is built and what it contains. It is a recipe for your container and gives you tremendous flexibility to construct almost any execution environment you can imagine. Here. we use the Dockerfile to describe a pretty standard python science stack and the simple scripts that we're going to add to it. See the [Dockerfile reference][dockerfile] for what's possible here.
20
20
21
-
*__build\_and\_push.sh__: The script to build the Docker image (using the Dockerfile above) and push it to the [Amazon EC2 Container Registry (ECR)][ecr] so that it can be deployed to IM. Specify the name of the image as the argument to this script. The script will generate a full name for the repository in your account and your configured AWS region. If this ECR repository doesn't exist, the script will create it.
21
+
*__build\_and\_push.sh__: The script to build the Docker image (using the Dockerfile above) and push it to the [Amazon EC2 Container Registry (ECR)][ecr] so that it can be deployed to SageMaker. Specify the name of the image as the argument to this script. The script will generate a full name for the repository in your account and your configured AWS region. If this ECR repository doesn't exist, the script will create it.
22
22
23
23
*__im-decision-trees__: The directory that contains the application to run in the container. See the next session for details about each of the files.
24
24
@@ -46,7 +46,7 @@ The subdirectory local-test contains scripts and sample data for testing the bui
46
46
47
47
#### The directory tree mounted into the container
48
48
49
-
The tree under test-dir is mounted into the container and mimics the directory structure that IM would create for the running container during training or hosting.
49
+
The tree under test-dir is mounted into the container and mimics the directory structure that SageMaker would create for the running container during training or hosting.
50
50
51
51
*__input/config/hyperparameters.json__: The hyperparameters for the training job.
52
52
*__input/data/training/leaf_train.csv__: The training data.
0 commit comments