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
Administrative date change with no evidence of security impact. The existing security improvement mention remains unchanged and doesn't address specific vulnerabilities or new security capabilities.
Diff
diff --git a/sagemaker/latest/dg/debugger-built-in-rules-configuration.md b/sagemaker/latest/dg/debugger-built-in-rules-configuration.md index 6aadccda2..ddb99e2cd 100644 --- a//sagemaker/latest/dg/debugger-built-in-rules-configuration.md +++ b//sagemaker/latest/dg/debugger-built-in-rules-configuration.md @@ -11 +11 @@ -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).