AWS m2 documentation change
Summary
Changed service deprecation date from July 30, 2026 to June 30, 2026
Security assessment
Administrative update to service timeline. No evidence of security vulnerability remediation or new security documentation.
Diff
diff --git a/m2/latest/userguide/applications-m2-cancel-batch-job.md b/m2/latest/userguide/applications-m2-cancel-batch-job.md index 19210163e..a9f22790e 100644 --- a//m2/latest/userguide/applications-m2-cancel-batch-job.md +++ b//m2/latest/userguide/applications-m2-cancel-batch-job.md @@ -9 +9 @@ Cancel a batch job -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).