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. While the notice mentions ongoing security investments, this specific change doesn't address any vulnerability or security incident. No security features or vulnerabilities are documented.
Diff
diff --git a/m2/latest/userguide/applications-m2-other-resources-structure.md b/m2/latest/userguide/applications-m2-other-resources-structure.md index 78126d90c..86d76b6ce 100644 --- a//m2/latest/userguide/applications-m2-other-resources-structure.md +++ b//m2/latest/userguide/applications-m2-other-resources-structure.md @@ -9 +9 @@ Managing an application's Java options -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).