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
Date-only administrative update. The persistent mention of security improvements is unchanged and doesn't reference any specific security issues, vulnerabilities, or new security features.
Diff
diff --git a/sagemaker/latest/dg/debugger-built-in-rules.md b/sagemaker/latest/dg/debugger-built-in-rules.md index 927ae0c43..b3f6a2b44 100644 --- a//sagemaker/latest/dg/debugger-built-in-rules.md +++ b//sagemaker/latest/dg/debugger-built-in-rules.md @@ -13 +13 @@ Debugger ruleCreateXGBoostReportDeadReluExplodingTensorPoorWeightInitializationS -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).