AWS m2 documentation change
Summary
Updated effective date for closing new customer access from July 30, 2026 to June 30, 2026
Security assessment
No security implications detected. Change only accelerates service sunset timeline without modifying security guidance or features.
Diff
diff --git a/m2/latest/userguide/mf-runtime-setup-mf-instance.md b/m2/latest/userguide/mf-runtime-setup-mf-instance.md index 392ca2e33..ac0924495 100644 --- a//m2/latest/userguide/mf-runtime-setup-mf-instance.md +++ b//m2/latest/userguide/mf-runtime-setup-mf-instance.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).