AWS m2 documentation change
Summary
Updated effective date for closing new customer access from July 30, 2026 to June 30, 2026
Security assessment
Change only adjusts a service availability date. Existing text about security improvements remains unchanged with no new security details added.
Diff
diff --git a/m2/latest/userguide/ba-runtime-config.md b/m2/latest/userguide/ba-runtime-config.md index 3ff4d29f1..85f09157f 100644 --- a//m2/latest/userguide/ba-runtime-config.md +++ b//m2/latest/userguide/ba-runtime-config.md @@ -9 +9 @@ Application configuration basicsApplication precedenceJNDI for databasesOther fi -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).