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: OPERATIONS.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,7 @@ Having created the A/B Testing Deployment Pipeline, this operations manual provi
4
4
5
5
## A/B Testing for Machine Learning models
6
6
7
-
Successful A/B Testing for machine learning models requires measuring how effective predictions are against end users.
8
-
It is important to be able to identify users consistently and be able to attribute success actions against the model predictions back to users.
7
+
Successful A/B Testing for machine learning models requires measuring how effective predictions are against end users. It is important to be able to identify users consistently and be able to attribute success actions against the model predictions back to users.
9
8
10
9
### Conversion Metrics
11
10
@@ -46,7 +45,11 @@ The configuration is stored in the CodeCommit source repository by stage name eg
46
45
*`epsilon` - The epsilon parameter used by the `EpsilonGreedy` strategy.
47
46
*`warmup` - The number of invocations to warm up before applying the strategy.
48
47
49
-
In addition to the above, you must specify the `champion` and `challenger` model variants for the deployment.
48
+
In addition to the above, you must specify the `champion` and `challenger` model variants for the deployment.
49
+
50
+
These will be loaded from the two Model Package Groups in the registry that include the project name and suffixed with `champion` or `challenger` for example project name `ab-testing-pipeline` these model package groups in the sample notebook:
|`api_name`| The API Gateway Name | "ab-testing" |
148
148
|`stage_name`| The stage namespace for resource and API Gateway path | "dev" |
149
-
|`endpoint_filter`| A prefix to filter which Amazon SageMaker endpoints the API can invoke| "*"|
149
+
|`endpoint_prefix`| A prefix to filter which Amazon SageMaker endpoints the API can invoked.| "" |
150
150
|`api_lambda_memory`| The [lambda memory](https://docs.aws.amazon.com/lambda/latest/dg/configuration-memory.html) allocation for API endpoint. | 768 |
151
151
|`api_lambda_timeout`| The lambda timeout for the API endpoint. | 10 |
152
152
|`metrics_lambda_memory`| The [lambda memory](https://docs.aws.amazon.com/lambda/latest/dg/configuration-memory.html) allocated for metrics processing Lambda | 768 |
@@ -164,9 +164,7 @@ Run the following command to deploy the API and testing infrastructure, optional
164
164
cdk deploy ab-testing-api
165
165
```
166
166
167
-
This stack will ask you to confirm any changes, and output the `RegisterLambda` which you will provide to the MLOps Project, and the `ApiEndpoint` which you will provide to the A/B Testing sample notebook.
168
-
169
-
Amazon SageMaker Studio projects will be granted access to invoke the Register Lambda, so if you are seeing errors running the above command ensure you have [Enable SageMaker project templates for Studio users](https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-projects-studio-updates.html).
167
+
This stack will ask you to confirm any changes, and output the `ApiEndpoint` which you will provide to the A/B Testing sample notebook.
170
168
171
169
## Create the SageMaker MLOps Project Template
172
170
@@ -276,7 +274,6 @@ On the Create project page, SageMaker templates is chosen by default. This optio
276
274
- The project name must have 32 characters or fewer.
277
275
10. In the Project template parameters, provide the *Repository Name** you created previously eg:
278
276
- For **StageName**, enter `dev`
279
-
- For **RegisterLambda**, enter the `RegisterLambda` output from the `ab-testing-api` stack
280
277
- For **CodeCommitSeedBucket**, enter the `CodeCommitSeedBucket` output from the `ab-testiing-service-catalog` stack
281
278
- For **CodeCommitSeedKey**, enter the `CodeCommitSeedKey` output from the `ab-testiing-service-catalog` stack
Once you have created a SageMaker Project, you can test the **Build** and **Register**stages locally by setting some environment variables, and running the commands found in the `buildspec` defined in the pipeline.
24
+
Once you have created a SageMaker Project, you can test the **Build**stage and **Register**events locally by setting some environment variables.
23
25
24
26
### Build Stage
25
27
@@ -32,12 +34,11 @@ export STAGE_NAME="dev"
32
34
cdk synth
33
35
```
34
36
35
-
### Register Stage
37
+
### Register
36
38
37
39
Export the environment variable for the `REGISTER_LAMBDA` created as part of the `ab-testing-api` stack, then run `register.py` file.
0 commit comments