Fairness and Explainability with SageMaker Clarify


This notebook takes approximately 30 minutes to run.


  1. Overview

  2. Prerequisites and Data

    1. Import Libraries

    2. Set Configurations

    3. Download data

    4. Loading the data: Adult Dataset

    5. Data inspection

    6. Encode and Upload the Dataset

  3. Train and Deploy XGBoost Model

    1. Train Model

    2. Create Model

  4. Amazon SageMaker Clarify

    1. Detecting Bias

      1. Writing DataConfig

      2. Writing ModelConfig

      3. Writing ModelPredictedLabelConfig

      4. Writing BiasConfig

      5. Pre-training Bias

      6. Post-training Bias

      7. Viewing the Bias Report

    2. Explaining Predictions

      1. Viewing the Explainability Report

      2. Analysis of local explanations

  5. Clean Up


Amazon SageMaker Clarify helps improve your machine learning models by detecting potential bias and helping explain how these models make predictions. The fairness and explainability functionality provided by SageMaker Clarify takes a step towards enabling AWS customers to build trustworthy and understandable machine learning models. The product comes with the tools to help you with the following tasks.

  • Measure biases that can occur during each stage of the ML lifecycle (data collection, model training and tuning, and monitoring of ML models deployed for inference).

  • Generate model governance reports targeting risk and compliance teams and external regulators.

  • Provide explanations of the data, models, and monitoring used to assess predictions.

This sample notebook walks you through:
1. Key terms and concepts needed to understand SageMaker Clarify 1. Measuring the pre-training bias of a dataset and post-training bias of a model 1. Explaining the importance of the various input features on the model’s decision 1. Accessing the reports through SageMaker Studio if you have an instance set up.

In doing so, the notebook first trains a SageMaker XGBoost model using training dataset, then use Amazon SageMaker Python SDK to launch SageMaker Clarify jobs to analyze an example dataset in CSV format.

SageMaker Clarify also supports analyzing dataset in SageMaker JSON Lines dense format, which is illustrated in another notebook. Additionally, there is a peer example available that utilizes the AWS SDK for Python to launch SageMaker Clarify jobs to analyze data in CSV format.

Prerequisites and Data

Import Libraries

import pandas as pd
import numpy as np
import os
import boto3
from datetime import datetime
from sagemaker import get_execution_role, session

Set Configurations

# Initialize sagemaker session
sagemaker_session = session.Session()

region = sagemaker_session.boto_region_name
print(f"Region: {region}")

role = get_execution_role()
print(f"Role: {role}")

bucket = sagemaker_session.default_bucket()

prefix = "sagemaker/DEMO-sagemaker-clarify"
Region: ap-south-1
Role: arn:aws:iam::000000000000:role/service-role/SMClarifySageMaker-ExecutionRole

Download data

Data Source: https://archive.ics.uci.edu/ml/machine-learning-databases/adult/

Let’s download the data and save it in the local folder with the name adult.data and adult.test from UCI repository\(^{[2]}\).

\(^{[2]}\)Dua Dheeru, and Efi Karra Taniskidou. “UCI Machine Learning Repository”. Irvine, CA: University of California, School of Information and Computer Science (2017).

from sagemaker.s3 import S3Downloader

adult_columns = [
    "Marital Status",
    "Ethnic group",
    "Capital Gain",
    "Capital Loss",
    "Hours per week",
if not os.path.isfile("adult.data"):
            "sagemaker-sample-files", "datasets/tabular/uci_adult/adult.data"
    print("adult.data saved!")
    print("adult.data already on disk.")

if not os.path.isfile("adult.test"):
            "sagemaker-sample-files", "datasets/tabular/uci_adult/adult.test"
    print("adult.test saved!")
    print("adult.test already on disk.")
adult.data already on disk.
adult.test already on disk.

Loading the data: Adult Dataset

From the UCI repository of machine learning datasets, this database contains 14 features concerning demographic characteristics of 45,222 rows (32,561 for training and 12,661 for testing). The task is to predict whether a person has a yearly income that is more or less than $50,000.

Here are the features and their possible values:

  1. Age: continuous.

  2. Workclass: Private, Self-emp-not-inc, Self-emp-inc, Federal-gov, Local-gov, State-gov, Without-pay, Never-worked.

  3. Fnlwgt: continuous (the number of people the census takers believe that observation represents).

  4. Education: Bachelors, Some-college, 11th, HS-grad, Prof-school, Assoc-acdm, Assoc-voc, 9th, 7th-8th, 12th, Masters, 1st-4th, 10th, Doctorate, 5th-6th, Preschool.

  5. Education-num: continuous.

  6. Marital-status: Married-civ-spouse, Divorced, Never-married, Separated, Widowed, Married-spouse-absent, Married-AF-spouse.

  7. Occupation: Tech-support, Craft-repair, Other-service, Sales, Exec-managerial, Prof-specialty, Handlers-cleaners, Machine-op-inspct, Adm-clerical, Farming-fishing, Transport-moving, Priv-house-serv, Protective-serv, Armed-Forces.

  8. Relationship: Wife, Own-child, Husband, Not-in-family, Other-relative, Unmarried.

  9. Ethnic group: White, Asian-Pac-Islander, Amer-Indian-Eskimo, Other, Black.

  10. Sex: Female, Male.

    • Note: this data is extracted from the 1994 Census and enforces a binary option on Sex

  11. Capital-gain: continuous.

  12. Capital-loss: continuous.

  13. Hours-per-week: continuous.

  14. Native-country: United-States, Cambodia, England, Puerto-Rico, Canada, Germany, Outlying-US(Guam-USVI-etc), India, Japan, Greece, South, China, Cuba, Iran, Honduras, Philippines, Italy, Poland, Jamaica, Vietnam, Mexico, Portugal, Ireland, France, Dominican-Republic, Laos, Ecuador, Taiwan, Haiti, Columbia, Hungary, Guatemala, Nicaragua, Scotland, Thailand, Yugoslavia, El-Salvador, Trinadad&Tobago, Peru, Hong, Holand-Netherlands.

Next, we specify our binary prediction task:

  1. Target: <=50,000, >$50,000.

training_data = pd.read_csv(
    "adult.data", names=adult_columns, sep=r"\s*,\s*", engine="python", na_values="?"

testing_data = pd.read_csv(
    "adult.test", names=adult_columns, sep=r"\s*,\s*", engine="python", na_values="?", skiprows=1

Age Workclass fnlwgt Education Education-Num Marital Status Occupation Relationship Ethnic group Sex Capital Gain Capital Loss Hours per week Country Target
0 39 State-gov 77516 Bachelors 13 Never-married Adm-clerical Not-in-family White Male 2174 0 40 United-States <=50K
1 50 Self-emp-not-inc 83311 Bachelors 13 Married-civ-spouse Exec-managerial Husband White Male 0 0 13 United-States <=50K
2 38 Private 215646 HS-grad 9 Divorced Handlers-cleaners Not-in-family White Male 0 0 40 United-States <=50K
3 53 Private 234721 11th 7 Married-civ-spouse Handlers-cleaners Husband Black Male 0 0 40 United-States <=50K
4 28 Private 338409 Bachelors 13 Married-civ-spouse Prof-specialty Wife Black Female 0 0 40 Cuba <=50K

Data inspection

Plotting histograms for the distribution of the different features is a good way to visualize the data. Let’s plot a few of the features that can be considered sensitive.
Let’s take a look specifically at the Sex feature of a census respondent. In the first plot we see that there are fewer Female respondents as a whole but especially in the positive outcomes, where they form ~\(\frac{1}{7}\)th of respondents.
%matplotlib inline
training_data["Sex"].value_counts().sort_values().plot(kind="bar", title="Counts of Sex", rot=0)
<AxesSubplot:title={'center':'Counts of Sex'}>
training_data["Sex"].where(training_data["Target"] == ">50K").value_counts().sort_values().plot(
    kind="bar", title="Counts of Sex earning >$50K", rot=0
<AxesSubplot:title={'center':'Counts of Sex earning >$50K'}>

Encode and Upload the Dataset

Here we encode the training and test data. Encoding input data is not necessary for SageMaker Clarify, but is necessary for the model.

from sklearn import preprocessing

def number_encode_features(df):
    result = df.copy()
    encoders = {}
    for column in result.columns:
        if result.dtypes[column] == np.object:
            encoders[column] = preprocessing.LabelEncoder()
            result[column] = encoders[column].fit_transform(result[column].fillna("None"))
    return result, encoders

training_data = pd.concat([training_data["Target"], training_data.drop(["Target"], axis=1)], axis=1)
training_data, _ = number_encode_features(training_data)
training_data.to_csv("train_data.csv", index=False, header=False)

testing_data, _ = number_encode_features(testing_data)
test_features = testing_data.drop(["Target"], axis=1)
test_target = testing_data["Target"]
test_features.to_csv("test_features.csv", index=False, header=False)

A quick note about our encoding: the “Female” Sex value has been encoded as 0 and “Male” as 1.

Target Age Workclass fnlwgt Education Education-Num Marital Status Occupation Relationship Ethnic group Sex Capital Gain Capital Loss Hours per week Country
0 0 39 5 77516 9 13 4 0 1 4 1 2174 0 40 38
1 0 50 4 83311 9 13 2 3 0 4 1 0 0 13 38
2 0 38 2 215646 11 9 0 5 1 4 1 0 0 40 38
3 0 53 2 234721 1 7 2 5 0 2 1 0 0 40 38
4 0 28 2 338409 9 13 2 9 5 2 0 0 0 40 4

Lastly, let’s upload the data to S3.

from sagemaker.s3 import S3Uploader
from sagemaker.inputs import TrainingInput

train_uri = S3Uploader.upload("train_data.csv", "s3://{}/{}".format(bucket, prefix))
train_input = TrainingInput(train_uri, content_type="csv")
test_uri = S3Uploader.upload("test_features.csv", "s3://{}/{}".format(bucket, prefix))

Train XGBoost Model

Train Model

Since our focus is on understanding how to use SageMaker Clarify, we keep it simple by using a standard XGBoost model.

It takes about 5 minutes for the model to be trained.

from sagemaker.image_uris import retrieve
from sagemaker.estimator import Estimator

# This references the AWS managed XGBoost container
xgboost_image_uri = retrieve("xgboost", region, version="1.5-1")

xgb = Estimator(


xgb.fit({"train": train_input}, logs=False)
INFO:sagemaker:Creating training-job with name: sagemaker-xgboost-2023-02-07-05-54-36-442

2023-02-07 05:54:36 Starting - Starting the training job..
2023-02-07 05:54:50 Starting - Preparing the instances for training........
2023-02-07 05:55:32 Downloading - Downloading input data....
2023-02-07 05:55:57 Training - Downloading the training image...
2023-02-07 05:56:18 Training - Training image download completed. Training in progress.......
2023-02-07 05:56:53 Uploading - Uploading generated training model.
2023-02-07 05:57:04 Completed - Training job completed

Create Model

Here we create the SageMaker model.

model_name = "DEMO-clarify-model-{}".format(datetime.now().strftime("%d-%m-%Y-%H-%M-%S"))
model = xgb.create_model(name=model_name)
container_def = model.prepare_container_def()
sagemaker_session.create_model(model_name, role, container_def)
INFO:sagemaker:Creating model with name: DEMO-clarify-model-07-02-2023-05-57-08

Amazon SageMaker Clarify

With your model set up, it’s time to explore SageMaker Clarify. For a general overview of how SageMaker Clarify processing jobs work, refer the provided link.

from sagemaker import clarify

# Initialize a SageMakerClarifyProcessor to compute bias metrics and model explanations.
clarify_processor = clarify.SageMakerClarifyProcessor(
    role=role, instance_count=1, instance_type="ml.m5.xlarge", sagemaker_session=sagemaker_session
INFO:sagemaker.image_uris:Defaulting to the only supported framework/algorithm version: 1.0.
INFO:sagemaker.image_uris:Ignoring unnecessary instance type: None.

Detecting Bias

SageMaker Clarify helps you detect possible pre-training and post-training biases using a variety of metrics.

Writing DataConfig

A DataConfig object communicates some basic information about data I/O to SageMaker Clarify. For our example here we provide the below information:

  • s3_data_input_path: S3 URI of the train dataset we uploaded above

  • s3_output_path: S3 URI at which our output report will be uploaded

  • label: Specifies the ground truth label, which is also known as observed label or target attribute. It is used for many bias metrics. In this example, the Target column has the ground truth label.

  • headers: The list of column names in the dataset

  • dataset_type: specifies the format of your dataset, for this example as we are using CSV dataset this will be text/csv

bias_report_output_path = "s3://{}/{}/clarify-bias".format(bucket, prefix)
bias_data_config = clarify.DataConfig(

Writing ModelConfig

A ModelConfig object communicates information about your trained model. To avoid additional traffic to the production models, SageMaker Clarify sets up and tears down a dedicated endpoint when processing. For our example here we provide the below information:

  • model_name: name of the concerned model, using name of the xgboost model trained earlier

  • instance_type and initial_instance_count specify your preferred instance type and instance count used to run your model on during SageMaker Clarify’s processing. The example dataset is small, so a single standard instance is good enough to run this example.

  • accept_type denotes the endpoint response payload format, and content_type denotes the payload format of request to the endpoint. As per the example model we created above both of these will be text/csv.

model_config = clarify.ModelConfig(

Writing ModelPredictedLabelConfig

A ModelPredictedLabelConfig provides information on the format of your predictions. XGBoost model outputs probabilities of samples, so SageMaker Clarify invokes the endpoint then uses probability_threshold to convert the probability to binary labels for bias analysis. Prediction above the threshold is interpreted as label value 1 and below or equal as label value 0.

predictions_config = clarify.ModelPredictedLabelConfig(probability_threshold=0.8)

Writing BiasConfig

BiasConfig contains configuration values for detecting bias using a Clarify container.

bias_config = clarify.BiasConfig(
    label_values_or_threshold=[1], facet_name="Sex", facet_values_or_threshold=[0], group_name="Age"

For our demo we provide the following information in BiasConfig API:

  • label_values_or_threshold: List of label value(s) or threshold to indicate positive outcome used for bias metrics. Here positive outcome is earning >$50,000.

  • facet_name: Sensitive columns of the dataset, “Sex” is the category

  • facet_values_or_threshold: values of the sensitive group, “Female” respondents are the sensitive group.

  • group_name: This example has selected the “Age” column which is used to form subgroups for the measurement of bias metric Conditional Demographic Disparity (CDD) or Conditional Demographic Disparity in Predicted Labels (CDDPL).

SageMaker Clarify can handle both categorical and continuous data for facet: values_or_threshold and for label_values_or_threshold. In this case we are using categorical data. The results will show if the model has a preference for records of one sex over the other.

Pre-training Bias

Bias can be present in your data before any model training occurs. Inspecting your data for bias before training begins can help detect any data collection gaps, inform your feature engineering, and help you understand what societal biases the data may reflect.

Computing pre-training bias metrics does not require a trained model.

Post-training Bias

Computing post-training bias metrics does require a trained model.

Unbiased training data (as determined by concepts of fairness measured by bias metric) may still result in biased model predictions after training. Whether this occurs depends on several factors including hyperparameter choices.

You can run these options separately with run_pre_training_bias() and run_post_training_bias() or at the same time with run_bias() as shown below. We use following additional parameters for the api call:

  • pre_training_methods: Pre-training bias metrics to be computed. The detailed description of the metrics can be found on Measure Pre-training Bias. This example sets methods to “all” to compute all the pre-training bias metrics.

  • post_training_methods: Post-training bias metrics to be computed. The detailed description of the metrics can be found on Measure Post-training Bias. This example sets methods to “all” to compute all the post-training bias metrics.

[ ]:
# The job takes about 10 minutes to run

Viewing the Bias Report

In Studio, you can view the results under the experiments tab.


Each bias metric has detailed explanations with examples that you can explore.


You could also summarize the results in a handy table!


If you’re not a Studio user yet, you can access the bias report in PDF, HTML and ipynb formats in the following S3 bucket:


Explaining Predictions

There are expanding business needs and legislative regulations that require explanations of why a model made the decision it did. SageMaker Clarify uses Kernel SHAP to explain the contribution that each input feature makes to the final decision.

For run_explainability API call we need similar DataConfig and ModelConfig objects we defined above. SHAPConfig here is the config class for Kernel SHAP algorithm.

For our demo we pass the following information in SHAPConfig:

  • baseline: Kernel SHAP algorithm requires a baseline (also known as background dataset). If not provided, a baseline is calculated automatically by SageMaker Clarify using K-means or K-prototypes in the input dataset. Baseline dataset type shall be the same as dataset_type, and baseline samples shall only include features. By definition, baseline should either be a S3 URI to the baseline dataset file, or an in-place list of samples. In this case we chose the latter, and put the mean of the train dataset to the list. For more details on baseline selection please refer this documentation.

  • num_samples: Number of samples to be used in the Kernel SHAP algorithm. This number determines the size of the generated synthetic dataset to compute the SHAP values.

  • agg_method: Aggregation method for global SHAP values. For our example here we are using mean_abs i.e. mean of absolute SHAP values for all instances

  • save_local_shap_values: Indicates whether to save the local SHAP values in the output location. Default is True.

explainability_output_path = "s3://{}/{}/clarify-explainability".format(bucket, prefix)
explainability_data_config = clarify.DataConfig(

baseline = [training_data.mean().iloc[1:].values.tolist()]
shap_config = clarify.SHAPConfig(
[ ]:
# The job takes about 10 minutes to run

Viewing the Explainability Report

As with the bias report, you can view the explainability report in Studio under the experiments tab.


The Model Insights tab contains direct links to the report and model insights.

If you’re not a Studio user yet, as with the Bias Report, you can access this report at the following S3 bucket.


Analysis of local explanations

It is possible to visualize the local explanations for single examples in your dataset. You can use the obtained results from running Kernel SHAP algorithm for global explanations.

You can simply load the local explanations stored in your output path, and visualize the explanation (i.e., the impact that the single features have on the prediction of your model) for any single example.

local_explanations_out = pd.read_csv(explainability_output_path + "/explanations_shap/out.csv")
feature_names = [str.replace(c, "_label0", "") for c in local_explanations_out.columns.to_series()]
local_explanations_out.columns = feature_names

selected_example = 111
    "Example number:",
    "\nwith model prediction:",
    sum(local_explanations_out.iloc[selected_example]) > 0,
print("\nFeature values -- Label", training_data.iloc[selected_example])
    kind="bar", title="Local explanation for the example number " + str(selected_example), rot=90
INFO:botocore.credentials:Found credentials from IAM Role: BaseNotebookInstanceEc2InstanceRole
Example number: 111
with model prediction: False

Feature values -- Label Target                 0
Age                   21
Workclass              2
fnlwgt            199915
Education             15
Education-Num         10
Marital Status         4
Occupation             7
Relationship           3
Ethnic group           4
Sex                    0
Capital Gain           0
Capital Loss           0
Hours per week        40
Country               38
Name: 120, dtype: int64
<AxesSubplot:title={'center':'Local explanation for the example number 111'}>

Note: You can run both bias and explainability jobs at the same time with run_bias_and_explainability(), refer API Documentation for more details.

Clean Up

Finally, don’t forget to clean up the resources we set up and used for this demo!

INFO:sagemaker:Deleting model with name: DEMO-clarify-model-07-02-2023-05-57-08