AWS m2 documentation change
Summary
Updated the effective date for closing new customer access to AWS Mainframe Modernization self-managed experience from July 30, 2026 to June 30, 2026.
Security assessment
The change modifies only a date field. The existing note about security improvements remains unaltered, with no evidence of security issue remediation.
Diff
diff --git a/m2/latest/userguide/ba-migration-notes.md b/m2/latest/userguide/ba-migration-notes.md index a7807e090..85664dfa7 100644 --- a//m2/latest/userguide/ba-migration-notes.md +++ b//m2/latest/userguide/ba-migration-notes.md @@ -9 +9 @@ Common upgradesMigrating from 3.10.0 to 4.0.0Migrating from 5.85.0 to 5.125.0 -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).