AWS prescriptive-guidance documentation change
Summary
Updated blog URL with anchor fragment for specific migration steps
Security assessment
The URL change only adds a text anchor for better navigation to migration instructions. No security vulnerabilities or features are referenced in the modified content.
Diff
diff --git a/prescriptive-guidance/latest/migration-microsoft-workloads-aws/migrating-failover-workloads.md b/prescriptive-guidance/latest/migration-microsoft-workloads-aws/migrating-failover-workloads.md index 25e8a7991..6ef83fe63 100644 --- a//prescriptive-guidance/latest/migration-microsoft-workloads-aws/migrating-failover-workloads.md +++ b//prescriptive-guidance/latest/migration-microsoft-workloads-aws/migrating-failover-workloads.md @@ -53 +53 @@ Consider your options for migrating to AWS, including a lift-and-shift approach - * **Traditional failover cluster migration** – If you're manually configuring a Microsoft failover cluster from scratch, you can follow the instructions in [Deploy SQL Server on Amazon EC2](https://docs.aws.amazon.com/sql-server-ec2/latest/userguide/create-sql-server-on-ec2-instance.html). Shared storage is one of the most important considerations for a failover cluster migration. Amazon EBS multi-attach doesn't support SCSI-3 Persistent Reservation, but [Amazon FSx for Windows File Server](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/what-is.html) and [Amazon FSx for NetApp ONTAP](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/what-is-fsx-ontap.html) both work well as shared storage options. One of the most common use cases is using an Always On Failover Cluster Instance for a SQL Server cluster with Amazon FSx for Windows File Server. For more information, see the [Simplify your Microsoft SQL Server high availability deployments using Amazon FSx for Windows File Server](https://aws.amazon.com/blogs/storage/simplify-your-microsoft-sql-server-high-availability-deployments-using-amazon-fsx-for-windows-file-server/) post in the AWS Storage Blog. The next step is bringing the nodes to the cloud. This can be achieved by using AWS Transform MGN. For more information, see the [Migrating your Microsoft Windows clusters to AWS using CloudEndure Migration](https://aws.amazon.com/blogs/storage/migrating-your-microsoft-windows-clusters-to-aws-using-cloudendure-migration/) post in the AWS Storage Blog. Then, you can configure a clustered role for your application to provide high availability. + * **Traditional failover cluster migration** – If you're manually configuring a Microsoft failover cluster from scratch, you can follow the instructions in [Deploy SQL Server on Amazon EC2](https://docs.aws.amazon.com/sql-server-ec2/latest/userguide/create-sql-server-on-ec2-instance.html). Shared storage is one of the most important considerations for a failover cluster migration. Amazon EBS multi-attach doesn't support SCSI-3 Persistent Reservation, but [Amazon FSx for Windows File Server](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/what-is.html) and [Amazon FSx for NetApp ONTAP](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/what-is-fsx-ontap.html) both work well as shared storage options. One of the most common use cases is using an Always On Failover Cluster Instance for a SQL Server cluster with Amazon FSx for Windows File Server. For more information, see the [Simplify your Microsoft SQL Server high availability deployments using Amazon FSx for Windows File Server](https://aws.amazon.com/blogs/storage/simplify-your-microsoft-sql-server-high-availability-deployments-using-amazon-fsx-for-windows-file-server/) post in the AWS Storage Blog. The next step is bringing the nodes to the cloud. This can be achieved by using AWS Transform MGN. For more information, see the [Migrating your Microsoft Windows clusters to AWS using CloudEndure Migration](https://aws.amazon.com/blogs/storage/migrating-your-microsoft-windows-clusters-to-aws-using-cloudendure-migration/#:~:text=Register%20for%20a%20CloudEndure%20account,for%20the%20replication%20to%20complete) post in the AWS Storage Blog. Then, you can configure a clustered role for your application to provide high availability.