AWS sagemaker documentation change
Summary
Updated effective date for closing new customer access to Amazon SageMaker Debugger from 6/30/26 to 7/30/26
Security assessment
Change only adjusts a service deprecation timeline without mentioning vulnerabilities, threats, or security patches. The reference to 'security improvements' is general maintenance, not evidence of addressing a specific security issue.
Diff
diff --git a/sagemaker/latest/dg/debugger-cloudwatch-lambda.md b/sagemaker/latest/dg/debugger-cloudwatch-lambda.md index f955959b4..f19c54be7 100644 --- a//sagemaker/latest/dg/debugger-cloudwatch-lambda.md +++ b//sagemaker/latest/dg/debugger-cloudwatch-lambda.md @@ -13 +13 @@ Example notebooks -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).