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 modifies a service sunset date without addressing vulnerabilities or security mechanisms. The mention of security improvements is pre-existing context, not part of the change.
Diff
diff --git a/sagemaker/latest/dg/debugger-stop-training.md b/sagemaker/latest/dg/debugger-stop-training.md index 67d3406b1..8bfd75643 100644 --- a//sagemaker/latest/dg/debugger-stop-training.md +++ b//sagemaker/latest/dg/debugger-stop-training.md @@ -13 +13 @@ Step 1: Create a Lambda functionStep 2: Configure the Lambda functionStep 3: Cre -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).