AWS sagemaker documentation change
Summary
Updated closure date for new customer access to Amazon SageMaker Debugger from 6/30/26 to 7/30/26
Security assessment
Service retirement date adjustment. Mentions security investments but provides no details about vulnerabilities or new security capabilities.
Diff
diff --git a/sagemaker/latest/dg/debugger-bring-your-own-container.md b/sagemaker/latest/dg/debugger-bring-your-own-container.md index bb4f819ca..ea3876433 100644 --- a//sagemaker/latest/dg/debugger-bring-your-own-container.md +++ b//sagemaker/latest/dg/debugger-bring-your-own-container.md @@ -13 +13 @@ Prepare to build a custom training containerRegister Debugger Hook to Your Train -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).