AWS m2 documentation change
Summary
Changed effective date for service closure to June 30, 2026
Security assessment
Date adjustment without security context modifications. Existing security commitment text is preserved verbatim.
Diff
diff --git a/m2/latest/userguide/ba-runtime-error-codes-h.md b/m2/latest/userguide/ba-runtime-error-codes-h.md index c1d1d56be..00f633977 100644 --- a//m2/latest/userguide/ba-runtime-error-codes-h.md +++ b//m2/latest/userguide/ba-runtime-error-codes-h.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).