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
The change only adjusts a service availability date without mentioning vulnerabilities, security patches, or incident response. No security implications are evident from the date change.
Diff
diff --git a/m2/latest/userguide/ba-runtime-rate-limiting.md b/m2/latest/userguide/ba-runtime-rate-limiting.md index 20e952b3f..519f5658e 100644 --- a//m2/latest/userguide/ba-runtime-rate-limiting.md +++ b//m2/latest/userguide/ba-runtime-rate-limiting.md @@ -9 +9 @@ Rate limiting overviewConfiguration propertiesEnable rate limitingClient identif -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).