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
Purely administrative date change with no security implications. The existing statement about security improvements remains unchanged and doesn't indicate any new security features or resolved vulnerabilities.
Diff
diff --git a/sagemaker/latest/dg/debugger-built-in-rules-api.CLI.md b/sagemaker/latest/dg/debugger-built-in-rules-api.CLI.md index ca7eb39da..4d9d84c1b 100644 --- a//sagemaker/latest/dg/debugger-built-in-rules-api.CLI.md +++ b//sagemaker/latest/dg/debugger-built-in-rules-api.CLI.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).