AWS m2 documentation change
Summary
Updated the 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 exclusively updates a service timeline date. The existing mention of security investments is unchanged and no security-specific documentation was added.
Diff
diff --git a/m2/latest/userguide/stop-environments-m2.md b/m2/latest/userguide/stop-environments-m2.md index 012410101..9ca5ae6c8 100644 --- a//m2/latest/userguide/stop-environments-m2.md +++ b//m2/latest/userguide/stop-environments-m2.md @@ -9 +9 @@ Stop a runtime environment -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).