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
The following are the high-level steps to deploy this solution:
7
8
8
9
1. Publish the SageMaker [MLOps Project template](https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-projects-templates.html) in the [AWS Service Catalog](https://aws.amazon.com/servicecatalog/)
@@ -88,13 +89,13 @@ sh install_layers.sh
88
89
89
90
This will enabling sample request to visualize the access patterns and drill into any specific errors.
AWS CDK requires permissions create AWS CloudFormation Stacks and the associated resources for your current execution role. If you have cloned this notebook into SageMaker Studio, you will need to add an inline policy to your SageMaker Studio execution role. You can find your user's role by browsing to the Studio dashboard.
Browse to the [IAM](https://console.aws.amazon.com/iam) section in the console, and find this role.
100
101
@@ -219,11 +220,11 @@ In this section you will publish the AWS Service Catalog template and Deploy the
219
220
220
221
In this step you will create a *Portfolio* and *Product* to provision a custom SageMaker MLOps Project template in the AWS Service Catalog and configure it so you can launch the project from within your SageMaker Studio domain. See more information on [customizing](docs/CUSTOM_TEMPLATE.md) the template, or import the template [manually](docs/SERVICE_CATALOG.md) into the AWS Service Catalog.
***AWS CodeCommit** seeded with the source from the [deployment_pipeline](deployment_pipeline)
226
-
***AWS CodeBuild** to query the **Amazon SageMaker Model Registry**and output **AWS CloudFormation**.
226
+
***AWS CodeCommit** seeded with the source from the [deployment_pipeline](deployment_pipeline).
227
+
***AWS CodeBuild** to produce **AWS CloudFormation**for deploying the **Amazon SageMaker Endpoint**.
227
228
***Amazon CloudWatch Event** to trigger the **AWS CodePipeline** for endpoint deployment.
228
229
229
230
Run the following command to deploy the MLOps project template, passing the required `ExecutionRoleArn` parameter. You can copy this from your SageMaker Studio dashboard as show above.
@@ -245,7 +246,7 @@ This stack will output the `CodeCommitSeedBucket` and `CodeCommitSeedKey` which
245
246
246
247
In this step you will deploy an Amazon API Gateway and supporting resources to enable dynamic A/B Testing of any Amazon SageMaker endpoint that has multiple production variants.
`NOTE`: If you have recently updated your AWS Service Catalog Project, you may need to refresh SageMaker Studio to ensure it picks up the latest version of your template.
294
295
@@ -305,7 +306,7 @@ Now that your project is ready, it’s time to train, register and approve a mod
305
306
3. Choose the Jupyter notebook you downloaded and upload it.
0 commit comments