AWS m2 documentation change
Summary
Modified service closure date from July 30, 2026 to June 30, 2026
Security assessment
Change affects only timeline information. Monitoring documentation remains unchanged with no security enhancements or vulnerability fixes introduced.
Diff
diff --git a/m2/latest/userguide/monitoring-cloudwatch.md b/m2/latest/userguide/monitoring-cloudwatch.md index ab010cc3a..cecd9a3ca 100644 --- a//m2/latest/userguide/monitoring-cloudwatch.md +++ b//m2/latest/userguide/monitoring-cloudwatch.md @@ -9 +9 @@ Runtime Environment MetricsApplication MetricsDimensions -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).