AWS sagemaker documentation change
Summary
Updated effective date for closing new customer access to Amazon SageMaker Clarify from 6/30/26 to 7/30/26
Security assessment
Change only adjusts a service deprecation timeline. No security vulnerability, exploit, or weakness is mentioned. Pre-existing text about security improvements remains unchanged.
Diff
diff --git a/sagemaker/latest/dg/clarify-model-explainability.md b/sagemaker/latest/dg/clarify-model-explainability.md index 29c2b36ab..344375bf0 100644 --- a//sagemaker/latest/dg/clarify-model-explainability.md +++ b//sagemaker/latest/dg/clarify-model-explainability.md @@ -13 +13 @@ Sample Notebooks -After careful consideration, we have made the decision to close new customer access to Amazon Sagemaker Clarify, effective 6/30/26. Existing customers can continue to use the service as normal. AWS continues to invest in security and availability improvements for Clarify, but we do not plan to introduce new features. For more information, see [Clarify availability change](./clarify-availability-change.html). +After careful consideration, we have made the decision to close new customer access to Amazon Sagemaker Clarify, effective 7/30/26. Existing customers can continue to use the service as normal. AWS continues to invest in security and availability improvements for Clarify, but we do not plan to introduce new features. For more information, see [Clarify availability change](./clarify-availability-change.html).