AWS sagemaker documentation change
Summary
Updated the effective date for closing new customer access to Amazon SageMaker Debugger from June 30, 2026 to July 30, 2026.
Security assessment
Only the deprecation date was modified. No security-related content was added, removed, or modified beyond the existing unchanged reference to ongoing security improvements.
Diff
diff --git a/sagemaker/latest/dg/debugger-built-in-rules-api.Boto3.md b/sagemaker/latest/dg/debugger-built-in-rules-api.Boto3.md index 3d07c10fa..33aaa5f4f 100644 --- a//sagemaker/latest/dg/debugger-built-in-rules-api.Boto3.md +++ b//sagemaker/latest/dg/debugger-built-in-rules-api.Boto3.md @@ -13 +13 @@ To configure a Debugger rule for debugging model parametersTo configure a Debugg -After careful consideration, we have made the decision to close new customer access to Amazon Sagemaker Debugger, effective 6/30/26. Existing customers can continue to use the service as normal. AWS continues to invest in security and availability improvements for Debugger, but we do not plan to introduce new features. For more information, see [Debugger availability change](./debugger-availability-change.html). +After careful consideration, we have made the decision to close new customer access to Amazon Sagemaker Debugger, effective 7/30/26. Existing customers can continue to use the service as normal. AWS continues to invest in security and availability improvements for Debugger, but we do not plan to introduce new features. For more information, see [Debugger availability change](./debugger-availability-change.html).