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 deprecation timeline was extended. No security-related content modifications were made, and the unchanged security improvement reference doesn't constitute new security documentation.
Diff
diff --git a/sagemaker/latest/dg/debugger-built-in-rules-example.md b/sagemaker/latest/dg/debugger-built-in-rules-example.md index 4e789025e..6117d073d 100644 --- a//sagemaker/latest/dg/debugger-built-in-rules-example.md +++ b//sagemaker/latest/dg/debugger-built-in-rules-example.md @@ -13 +13 @@ Debugger built-in rules example notebooksDebugger built-in rules example codeUse -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).