AWS m2 documentation change
Summary
Changed service sunset date from July 30 to June 30, 2026
Security assessment
Administrative date update without security implications. Existing security commitment statement remains identical.
Diff
diff --git a/m2/latest/userguide/update-environments-m2.md b/m2/latest/userguide/update-environments-m2.md index 11aff16cd..a4073b03f 100644 --- a//m2/latest/userguide/update-environments-m2.md +++ b//m2/latest/userguide/update-environments-m2.md @@ -9 +9 @@ Update a runtime environmentMaintenance window -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).