AWS sagemaker documentation change
Summary
Updated SageMaker Clarify new customer access closure date from 6/30/26 to 7/30/26
Security assessment
Change only adjusts service sunset date without modifying security content. Mentions existing security investments but doesn't introduce new security information or address vulnerabilities.
Diff
diff --git a/sagemaker/latest/dg/clarify-data-bias-metric-true-label-imbalance.md b/sagemaker/latest/dg/clarify-data-bias-metric-true-label-imbalance.md index 8b3fda40b..7ad33aad4 100644 --- a//sagemaker/latest/dg/clarify-data-bias-metric-true-label-imbalance.md +++ b//sagemaker/latest/dg/clarify-data-bias-metric-true-label-imbalance.md @@ -11 +11 @@ -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).