AWS launchwizard documentation change
Summary
Updated terminology from 'self-managed Active Directory' to 'Self Managed Active Directory' for consistency, expanded SQL Server support matrix to include Windows Server 2025 and SQL Server 2025, added Developer Edition variants, and adjusted documentation links.
Security assessment
Changes involve terminology standardization, version support updates, and link text adjustments. No concrete evidence of addressing security vulnerabilities or introducing new security features. The link modification to 'Self Managed-AD.html' appears to be a formatting change rather than a security-related update.
Diff
diff --git a/launchwizard/latest/userguide/launch-wizard-getting-started.md b/launchwizard/latest/userguide/launch-wizard-getting-started.md index 1ce6bde9d..258f04bc1 100644 --- a//launchwizard/latest/userguide/launch-wizard-getting-started.md +++ b//launchwizard/latest/userguide/launch-wizard-getting-started.md @@ -195 +195 @@ Show moreShow less -Launch Wizard can deploy SQL Server using AWS Directory Service for Microsoft Active Directory (AWS Managed Microsoft AD), or your self-managed Active Directory. +Launch Wizard can deploy SQL Server using AWS Directory Service for Microsoft Active Directory (AWS Managed Microsoft AD), or your Self Managed Active Directory. @@ -232 +232 @@ The following key operations are performed against your Active Directory by Laun -If you are [ deploying SQL Server into an existing VPC across multiple Availability Zones and connecting to a self-managed Active Directory ]() or [deploying SQL Server into an existing VPC on a single node and connecting to a self-managed Active Directory](), verify the following prerequisites. +If you are [ deploying SQL Server into an existing VPC across multiple Availability Zones and connecting to a Self Managed Active Directory ]() or [deploying SQL Server into an existing VPC on a single node and connecting to a Self Managed Active Directory](), verify the following prerequisites. @@ -234 +234 @@ If you are [ deploying SQL Server into an existing VPC across multiple Availabil - * If your self-managed Active Directory resides in another network than where you are deploying SQL Server, make sure you have connectivity between your VPC and the self-managed Active Directory network. You must also be able to connect to any DNS servers you specify during deployment from your VPC. For more information, see [Network-to-Amazon VPC connectivity options](https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/network-to-amazon-vpc-connectivity-options.html). + * If your Self Managed Active Directory resides in another network than where you are deploying SQL Server, make sure you have connectivity between your VPC and the Self Managed Active Directory network. You must also be able to connect to any DNS servers you specify during deployment from your VPC. For more information, see [Network-to-Amazon VPC connectivity options](https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/network-to-amazon-vpc-connectivity-options.html). @@ -295,4 +295,5 @@ While not exhaustive, the following requirements cover most of the configuration -Support matrix SQL Server Version | Windows Server 2019 | Windows Server 2022 ----|---|--- -SQL Server 2019 | YES | YES -SQL Server 2022 | YES | YES +Support matrix SQL Server Version | Windows Server 2019 | Windows Server 2022 | Windows Server 2025 +---|---|---|--- +SQL Server 2019 | YES | YES | YES +SQL Server 2022 | YES | YES | YES +SQL Server 2025 | YES | YES | YES @@ -312 +313,5 @@ SQL Server 2022 | YES | YES - * SQL Server Enterprise Edition 2022 or Standard Edition 2022 + * SQL Server Enterprise Edition 2022, Standard Edition 2022, or Developer Edition 2022 + + * SQL Server Standard Developer Edition 2025 + + * SQL Server Enterprise Developer Edition 2025 @@ -355 +360 @@ If you use a custom Linux AMI, you must adhere to the following requirements: -Launch Wizard uses continuously available Amazon FSx file shares to host clustered databases. The Amazon FSx file shares are accessible from within an instance joined to the domain. You can either create a new Active Directory or connect to an existing Active Directory (managed or self-managed). If you connect to an existing Active Directory, you can use preexisting security groups . The security groups must satisfy port and security requirements for FSx to communicate with the domain, as described in [Using Amazon FSx with your self-managed Microsoft Active Directory](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-managed-AD.html) and [Using Amazon FSx with AWS Directory Service for Microsoft Active Directory](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/fsx-aws-managed-ad.html). +Launch Wizard uses continuously available Amazon FSx file shares to host clustered databases. The Amazon FSx file shares are accessible from within an instance joined to the domain. You can either create a new Active Directory or connect to an existing Active Directory (managed or Self Managed). If you connect to an existing Active Directory, you can use preexisting security groups . The security groups must satisfy port and security requirements for FSx to communicate with the domain, as described in [Using Amazon FSx with your Self Managed Microsoft Active Directory](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/Self Managed-AD.html) and [Using Amazon FSx with AWS Directory Service for Microsoft Active Directory](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/fsx-aws-managed-ad.html). @@ -357 +362 @@ Launch Wizard uses continuously available Amazon FSx file shares to host cluster -If you are using an existing AWS Managed Active Directory instance, you must specify the ID of the managed Active Directory instance for FSx to be able to join the domain. The account must have the same access rights in the domain as described in [Using Amazon FSx with your self-managed Microsoft Active Directory](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-managed-AD.html) and [Using Amazon FSx with AWS Directory Service for Microsoft Active Directory](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/fsx-aws-managed-ad.html). +If you are using an existing AWS Managed Active Directory instance, you must specify the ID of the managed Active Directory instance for FSx to be able to join the domain. The account must have the same access rights in the domain as described in [Using Amazon FSx with your Self Managed Microsoft Active Directory](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-managed-AD.html) and [Using Amazon FSx with AWS Directory Service for Microsoft Active Directory](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/fsx-aws-managed-ad.html).