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
Administrative date change without security implications. The unchanged mention of security investments doesn't indicate any new security documentation or vulnerability fixes.
Diff
diff --git a/m2/latest/userguide/applications-m2-transactions.console.md b/m2/latest/userguide/applications-m2-transactions.console.md index e377ca8b5..4758935f9 100644 --- a//m2/latest/userguide/applications-m2-transactions.console.md +++ b//m2/latest/userguide/applications-m2-transactions.console.md @@ -9 +9 @@ Manage transactions for applications -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).