sagemaker: Support deployment guardrails for endpoints

[petermeansrock]

Describe the feature

As described in the SageMaker Endpoint L2 construct RFC:

Deployment Guardrails: By default, when updating an endpoint, SageMaker uses an all-at-once blue/green deployment strategy: a new fleet is provisioned with the new approrpriate configuration, and upon successful provisioning, the traffic is flipped and the old fleet is terminated. To augment this functionality, the DeploymentConfig attribute was added to the Endpoint resource which now allows (1) the specification of a CloudWatch alarm for auto-rollback and (2) additional deployment policies beyond all-at-once, including canary and linear deployment strategies (along with more fine-grained timing settings).

Please 👍 this issue to help with the prioritization of this feature.

Use Case

Customers will use this feature to (1) enable auto-rollback of endpoint deployments based on CloudWatch alarms and (2) control the deployment strategy (e.g., canary, linear).

Proposed Solution

As described in the SageMaker Endpoint L2 construct RFC:

Adding this functionlity should consist of incorporating new attribute(s) on the Endpoint L2 construct's props interface and plumbing it through to the underlying L1 resource definition. This work should also include support for the RetainDeploymentConfig boolean flag which controls whether to reuse the previous deployment configuration or use the new one. Note, there are a number of SageMaker features which prevent the use of deployment configuration, so defending against combinations of features may improve the customer experience with the Endpoint construct.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.54.0-alpha.0

Environment details (OS name and version, etc.)

macOS Ventura