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 in troubleshooting guide without security context. No vulnerabilities or security features are referenced in the change.
Diff
diff --git a/m2/latest/userguide/env-unhealthy.md b/m2/latest/userguide/env-unhealthy.md index 03fbb36cb..73a5a761d 100644 --- a//m2/latest/userguide/env-unhealthy.md +++ b//m2/latest/userguide/env-unhealthy.md @@ -9 +9 @@ Common causeResolution -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).