AWS m2 documentation change
Summary
Updated effective date for service access closure to June 30, 2026
Security assessment
Date-only modification. Security references remain identical to previous version with no new security information.
Diff
diff --git a/m2/latest/userguide/system-misc-utilities.md b/m2/latest/userguide/system-misc-utilities.md index 02f033c2e..96c480bf5 100644 --- a//m2/latest/userguide/system-misc-utilities.md +++ b//m2/latest/userguide/system-misc-utilities.md @@ -9 +9 @@ CBL_AND/CBL_OR/CBL_XOR/CBL_EQ/CBL_IMP/CBL_NOTCEE3ABDCEEDATECEELOCTCEERAN0CEESECS -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).