AWS m2 documentation change
Summary
Updated service closure date from July 30, 2026 to June 30, 2026
Security assessment
Routine date adjustment without security impact. Existing security improvement mentions remain unchanged.
Diff
diff --git a/m2/latest/userguide/ba-runtime-maint-container.md b/m2/latest/userguide/ba-runtime-maint-container.md index bb9eb13aa..64248b9ba 100644 --- a//m2/latest/userguide/ba-runtime-maint-container.md +++ b//m2/latest/userguide/ba-runtime-maint-container.md @@ -9 +9 @@ PrerequisitesUpgrade the AWS Transform for mainframe Runtime -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).