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
Purely administrative date change without security context. The notice references continued security investments but doesn't document any specific security features or issues.
Diff
diff --git a/m2/latest/userguide/ba-runtime-setup-onboard.md b/m2/latest/userguide/ba-runtime-setup-onboard.md index 88f914dac..73c5686bc 100644 --- a//m2/latest/userguide/ba-runtime-setup-onboard.md +++ b//m2/latest/userguide/ba-runtime-setup-onboard.md @@ -9 +9 @@ Regions and buckets for AWS Transform for mainframe RuntimeUsing the AWS CLI to -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).