AWS m2 documentation change
Summary
Changed service closure date from July 30, 2026 to June 30, 2026 for AWS Mainframe Modernization self-managed experience
Security assessment
Date adjustment doesn't alter security statements. The existing note about ongoing security investments remains identical.
Diff
diff --git a/m2/latest/userguide/tutorial-unikix-runtime.md b/m2/latest/userguide/tutorial-unikix-runtime.md index cf9418cb5..95d70b761 100644 --- a//m2/latest/userguide/tutorial-unikix-runtime.md +++ b//m2/latest/userguide/tutorial-unikix-runtime.md @@ -9 +9 @@ Deployment flow diagramPrerequisitesStep 1: Prepare the environmentStep 2: Creat -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).