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
The change only extends the service deprecation timeline by one month. There is no evidence of security vulnerability fixes, security incident references, or new security features. The mention of 'security improvements' is unchanged from previous documentation.
Diff
diff --git a/sagemaker/latest/dg/debugger-built-in-actions.md b/sagemaker/latest/dg/debugger-built-in-actions.md index 2c98d35f4..3b0bde483 100644 --- a//sagemaker/latest/dg/debugger-built-in-actions.md +++ b//sagemaker/latest/dg/debugger-built-in-actions.md @@ -13 +13 @@ Set up Amazon SNS, create an SMDebugRules topic, and subscribe to the topicSet u -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).