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
Date-only change in introductory section. No modifications to the 'Configuring security for the BAC' content that follows.
Diff
diff --git a/m2/latest/userguide/bac-deployment.md b/m2/latest/userguide/bac-deployment.md index 6e79cc025..5cc96cb22 100644 --- a//m2/latest/userguide/bac-deployment.md +++ b//m2/latest/userguide/bac-deployment.md @@ -9 +9 @@ BAC dedicated configuration fileConfiguring security for the BACInstalling the m -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).