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
Despite being in a security-focused file, the change only updates a service retirement date. No security configurations, vulnerabilities, or new security features are documented.
Diff
diff --git a/m2/latest/userguide/infrastructure-security.md b/m2/latest/userguide/infrastructure-security.md index cfb577961..6eaa1f9ac 100644 --- a//m2/latest/userguide/infrastructure-security.md +++ b//m2/latest/userguide/infrastructure-security.md @@ -7 +7 @@ -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).