AWS m2 documentation change
Summary
Updated the effective date for closing new customer access from July 30, 2026 to June 30, 2026
Security assessment
Change only adjusts a service timeline date. The text mentions ongoing security improvements but doesn't introduce new security documentation or address vulnerabilities.
Diff
diff --git a/m2/latest/userguide/m2wait.md b/m2/latest/userguide/m2wait.md index bb4fd9445..4b15358ec 100644 --- a//m2/latest/userguide/m2wait.md +++ b//m2/latest/userguide/m2wait.md @@ -9 +9 @@ Supported platformsConfigure M2WAIT for AWS Mainframe Modernization ManagedConfi -After careful consideration, we have made the decision to close new customer access to **AWS Mainframe Modernization self-managed experience** , effective July 30, 2026. Existing customers can continue to use the service as normal. AWS continues to invest in security and availability improvements for AWS Mainframe Modernization self-managed experience, but we do not plan to introduce new features. For more information, see [AWS Mainframe Modernization availability change](https://docs.aws.amazon.com/m2/latest/userguide/mainframe-modernization-availability-change.html). +After careful consideration, we have made the decision to close new customer access to **AWS Mainframe Modernization self-managed experience** , effective June 30, 2026. Existing customers can continue to use the service as normal. AWS continues to invest in security and availability improvements for AWS Mainframe Modernization self-managed experience, but we do not plan to introduce new features. For more information, see [AWS Mainframe Modernization availability change](https://docs.aws.amazon.com/m2/latest/userguide/mainframe-modernization-availability-change.html).