AWS m2 documentation change
Summary
Updated effective date for service access closure from July 30, 2026 to June 30, 2026
Security assessment
Date change only. No security vulnerability fixes or new security documentation added. Policy examples content remains unchanged.
Diff
diff --git a/m2/latest/userguide/security_iam_id-based-policy-examples.md b/m2/latest/userguide/security_iam_id-based-policy-examples.md index e7ae0ef69..991f80eb6 100644 --- a//m2/latest/userguide/security_iam_id-based-policy-examples.md +++ b//m2/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -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).