AWS m2 documentation change
Summary
Modified service access closure date from July 30 to June 30, 2026
Security assessment
Purely date adjustment with no security context changes. No vulnerabilities addressed or security features documented.
Diff
diff --git a/m2/latest/userguide/system-datasets-utilities.md b/m2/latest/userguide/system-datasets-utilities.md index a3bde26e0..f39df3258 100644 --- a//m2/latest/userguide/system-datasets-utilities.md +++ b//m2/latest/userguide/system-datasets-utilities.md @@ -9 +9 @@ BLUESAMCOPY/BLUESAMCREATE/BLUESAMDELETE/BLUESAMCLEARBPXWDYNGDGUTILSICEGENER/SYNC -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).