AWS m2 documentation change
Summary
Updated effective date for closing new customer access to AWS Mainframe Modernization self-managed experience from July 30, 2026 to June 30, 2026
Security assessment
Date modification without security content changes. The existing security commitment remains identical. No indicators of security incident response.
Diff
diff --git a/m2/latest/userguide/tutorial-filetransfer-getting-started.md b/m2/latest/userguide/tutorial-filetransfer-getting-started.md index eca493b65..6a58ad492 100644 --- a//m2/latest/userguide/tutorial-filetransfer-getting-started.md +++ b//m2/latest/userguide/tutorial-filetransfer-getting-started.md @@ -9 +9 @@ OverviewStep 1: Transfer the agent binaries tar package from AWS to the mainfram -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).