AWS m2 documentation change
Summary
Adjusted deprecation effective date from July 30, 2026 to June 30, 2026
Security assessment
Purely administrative date change. References to ongoing security improvements are maintained verbatim with no indication of security incidents or new security features.
Diff
diff --git a/m2/latest/userguide/mf-runtime-setup.md b/m2/latest/userguide/mf-runtime-setup.md index 5005c68a9..1e76c4bd2 100644 --- a//m2/latest/userguide/mf-runtime-setup.md +++ b//m2/latest/userguide/mf-runtime-setup.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).