Using Amazon Elastic Inference with MXNet on an Amazon SageMaker Notebook Instance

This notebook demonstrates how to enable and utilize Amazon Elastic Inference with our predefined SageMaker MXNet containers.

Amazon Elastic Inference (EI) is a resource you can attach to your Amazon EC2 instances to accelerate your deep learning (DL) inference workloads. EI allows you to add inference acceleration to an Amazon SageMaker hosted endpoint or Jupyter notebook for a fraction of the cost of using a full GPU instance. For more information please visit:

This notebook is an adaption of the SageMaker MXNet MNIST notebook, with modifications showing the changes needed to enable and use EI with MXNet on SageMaker.

  1. Using Amazon Elastic Inference with MXNet on an Amazon SageMaker Notebook Instance

  2. MNIST dataset

  3. Setup

  4. The training script

  5. SageMaker’s MXNet estimator class

  6. Running the Training job

  7. Creating an inference endpoint and attaching an EI accelerator

  8. How our models are loaded

  9. Using EI with a SageMaker notebook instance

  10. Making an inference request locally

  11. Delete the Endpoint

If you are familiar with SageMaker and already have a trained model, skip ahead to the Creating-an-inference-endpoint section

For this example, we will be utilizing the SageMaker Python SDK, which makes it easy to train and deploy MXNet models. In this example, we train a simple neural network using the Apache MXNet Module API and the MNIST dataset.

MNIST dataset

The MNIST dataset is widely used for handwritten digit classification, and consists of 70,000 labeled 28x28 pixel grayscale images of hand-written digits. The dataset is split into 60,000 training images and 10,000 test images. There are 10 classes (one for each of the 10 digits). The task at hand is to train a model using the 60,000 training images and subsequently test its classification accuracy on the 10,000 test images.


Let’s start by creating a SageMaker session and specifying the IAM role arn used to give training and hosting access to your data. See the documentation for how to create these. Note, if more than one role is required for notebook instances, training, and/or hosting, please replace the sagemaker.get_execution_role() with a the appropriate full IAM role arn string(s).

[ ]:
import sagemaker

role = sagemaker.get_execution_role()

This notebook shows how to use the SageMaker Python SDK to run your code in a local container before deploying to SageMaker’s managed training or hosting environments. Just change your estimator’s instance_type to local or local_gpu. For more information, see local mode.

To use Amazon Elastic Inference locally change your accelerator_type to local_sagemaker_notebook when calling deploy().

``local_sagemaker_notebook`` will only work if you created your notebook instance with an EI accelerator attached to it.

In order to use this feature you’ll need to install docker-compose (and nvidia-docker if training with a GPU). Running following script will install docker-compose or nvidia-docker-compose and configure the notebook environment for you.

Note, you can only run a single local notebook at a time.

[ ]:
!/bin/bash ./

The training script

The script provides all the code we need for training and hosting a SageMaker model. The script also checkpoints the model at the end of every epoch and saves the model graph, params and optimizer state in the folder /opt/ml/checkpoints. If the folder path does not exist then it will skip checkpointing. The script we will use is adaptated from Apache MXNet MNIST tutorial.

[ ]:

SageMaker’s MXNet estimator class

The SageMaker MXNet estimator allows us to run single machine or distributed training in SageMaker, using CPU or GPU-based instances.

When we create the estimator, we pass in the filename of our training script, the name of our IAM execution role, and the S3 locations we defined in the setup section. We also provide a few other parameters. instance_count and instance_type determine the number and type of SageMaker instances that will be used for the training job. The hyperparameters parameter is a dict of values that will be passed to your training script – you can see how to access these values in the script above.

For this example, we will train our model on the local instance this notebook is running on. This is achieved by using local for instance_type. By passing local, training will be done inside of a Docker container on this notebook instance.

[ ]:
from sagemaker.mxnet import MXNet

mnist_estimator = MXNet(
    hyperparameters={"learning-rate": 0.1},

Running the Training job

After we’ve constructed our MXNet object, we can fit it using data stored in S3. Below we run SageMaker training on two input channels: train and test.

During training, SageMaker makes this data stored in S3 available in the local filesystem where the mnist script is running. The script simply loads the train and test data from disk.

[ ]:
import boto3

region = boto3.Session().region_name
train_data_location = "s3://sagemaker-sample-data-{}/mxnet/mnist/train".format(region)
test_data_location = "s3://sagemaker-sample-data-{}/mxnet/mnist/test".format(region){"train": train_data_location, "test": test_data_location})

Creating an inference endpoint and attaching an EI accelerator

After training, we use the MXNet estimator object to build and deploy an MXNetPredictor. This creates a Sagemaker endpoint – a hosted prediction service that we can use to perform inference.

The arguments to the deploy allows us to set the following:

  • instance_count - how many instances to back the endpoint.

  • instance_type - which EC2 instance type to use for the endpoint. For information on supported instance, please check here.

  • accelerator_type - determines which EI accelerator type to attach to each of our instances. The supported types of accelerators can be found here:

How our models are loaded

You should provide your custom model_fn to use EI accelerator attached to your endpoint. An example of model_fn implementation is as follows:

def model_fn(model_dir):

    ctx = mx.cpu()
    sym, args, aux = mx.model.load_checkpoint(os.path.join(model_dir, 'model'), 0)
    sym = sym.optimize_for('EIA')

    mod = mx.mod.Module(symbol=sym, context=ctx, data_names=data_names, label_names=None)
    mod.bind(for_training=False, data_shapes=data_shapes)
    mod.set_params(args, aux, allow_missing=True)

    return mod

Check above for the specific implementation of model_fn() in this notebook example.

In EI MXNet 1.5.1 and earlier, the predefined SageMaker MXNet containers have a default model_fn, which determines how your model is loaded. The default model_fn loads an MXNet Module object with a context based on the instance type of the endpoint.

If an EI accelerator is attached to your endpoint and a custom model_fn isn’t provided, then the default model_fn will load the MXNet Module object. This default model_fn works with the default save function. If a custom save function was defined, then you may need to write a custom model_fn function. For more information on model_fn, see this documentation for using MXNet with SageMaker.

For examples on how to load and serve a MXNet Module object explicitly, please see our predefined default ``model_fn` for MXNet <>`__.

Using EI with a SageMaker notebook instance

Here we’re going to utilize the EI accelerator attached to our local SageMaker notebook instance. This can be done by using local_sagemaker_notebook as the value for accelerator_type. This will make an inference request against the MXNet endpoint running on this Notebook Instance with an attached EI.

An EI accelerator must be attached in order to make inferences using EI.

As of now, an EI accelerator attached to a notebook will initialize for the first deep learning framework used to inference against EI. If you wish to use EI with another deep learning framework, please either restart or create a new notebook instance with the new EI.

``local_sagemaker_notebook`` will only work if you created your notebook instance with an EI accelerator attached to it.

Please restart or create a new notebook instance if you wish to use EI with a different framework than the first framework used on this notebook instance as specified when calling ``deploy()`` with ``local_sagemaker_notebook``for ``accelerator_type``.

[ ]:

predictor = mnist_estimator.deploy(
    initial_instance_count=1, instance_type="local", accelerator_type="local_sagemaker_notebook"

The request handling behavior of the Endpoint is determined by the script. In this case, the script doesn’t include any request handling functions, so the Endpoint will use the default handlers provided by SageMaker. These default handlers allow us to perform inference on input data encoded as a multi-dimensional JSON array.

Making an inference request locally

Now that our Endpoint is deployed and we have a predictor object, we can use it to classify handwritten digits.

To see inference in action, draw a digit in the image box below. The pixel data from your drawing will be loaded into a data variable in this notebook.

Note: after drawing the image, you’ll need to move to the next notebook cell.

[ ]:
from IPython.display import HTML


Now we can use the predictor object to classify the handwritten digit:

[ ]:
response = predictor.predict(data)
print("Raw prediction result:")

labeled_predictions = list(zip(range(10), response[0]))
print("Labeled predictions: ")

labeled_predictions.sort(key=lambda label_and_prob: 1.0 - label_and_prob[1])
print("Most likely answer: {}".format(labeled_predictions[0]))

Delete the endpoint

After you have finished with this example, remember to delete the prediction endpoint to release the instance(s) associated with it.

[ ]:
print("Endpoint name: " + predictor.endpoint)
[ ]:
import sagemaker

[ ]: