AWS m2 documentation change
Summary
Updated effective date for closing new customer access to AWS Mainframe Modernization self-managed experience from July 30, 2026 to June 30, 2026
Security assessment
The change only adjusts a service sunset date without modifying security content. The existing mention of security improvements remains unchanged. No vulnerability or security incident is referenced.
Diff
diff --git a/m2/latest/userguide/troubleshooting-m2.md b/m2/latest/userguide/troubleshooting-m2.md index b3fea2df6..a7e69fdf5 100644 --- a//m2/latest/userguide/troubleshooting-m2.md +++ b//m2/latest/userguide/troubleshooting-m2.md @@ -7 +7 @@ -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).