AWS mgn: Restructure FSx for ONTAP MGN integration guide; add ARP, secrets, key guidance
Summary
Reorganizes the FSx for ONTAP target storage documentation: rewrites storage/throughput capacity sizing guidance, adds a new 'File system settings for MGN' section covering Autonomous Ransomware Protection (ARP) and maintenance windows, clarifies PKCS#8 private key conversion, tightens Secrets Manager secret key-name requirements (cert/key, no username), and rewords the AWS managed roles reinitialization note.
Security assessment
The change is a documentation restructure, not a fix for a specific vulnerability. It does add security-adjacent operational guidance: it tells users to disable ONTAP Autonomous Ransomware Protection during migration (a security feature trade-off), reinforces exact Secrets Manager key names (cert/key, no username) for client certificate credentials, and clarifies PKCS#8 private key format handling. These are credential/config best-practice notes rather than remediation of a disclosed weakness.
Evidence
+ * **Autonomous Ransomware Protection (ARP)** : If ONTAP ARP is enabled on the file system, disable it before migration. Otherwise, ARP can prevent MGN from deleting replication volumes.
Diff
diff --git a/mgn/latest/ug/fsx-ontap.md b/mgn/latest/ug/fsx-ontap.md index 093649d..846beca 100644 --- a//mgn/latest/ug/fsx-ontap.md +++ b//mgn/latest/ug/fsx-ontap.md @@ -19 +19 @@ FSx for ONTAP as a target storage type is available in all AWS Regions where bot -Do not rename or modify MGN-managed FSx for ONTAP resources (LUNs, igroups, snapshots). Changes to these resources disrupt migration and require restarting the migration from the beginning. +Do not rename or modify MGN-managed FSx for ONTAP resources, such as logical unit numbers (LUNs), igroups, and snapshots. Changes to these resources disrupt migration and require restarting the migration from the beginning. @@ -46,3 +46 @@ Before integrating FSx for ONTAP with MGN, ensure the following: -###### Important - -If you initialized MGN before FSx for ONTAP support was available, you must reinitialize the service to create the required AWS managed roles. In the MGN console, navigate to **Settings → Replication template** and choose **Reinitialize Service Permissions**. For details on these roles and their managed policies, see [AWS Transform MGN managed policies](./security-iam-awsmanpol.html). +If you initialized MGN before FSx for ONTAP support was available, reinitialize the service to create the required AWS managed roles. In the MGN console, navigate to **Settings → Replication template** and choose **Reinitialize Service Permissions**. For information about these roles and their managed policies, see [AWS Transform MGN managed policies](./security-iam-awsmanpol.html). @@ -74,2 +71,0 @@ Create this security group in the VPC where MGN will launch target instances. -###### Important - @@ -177 +173,5 @@ MGN can work with an existing FSx for ONTAP file system or a new one. If you do -###### Important for MGN integration +For instructions on creating and configuring FSx for ONTAP file systems, see [Creating FSx for ONTAP file systems](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/creating-file-systems.html). + +### File system settings for MGN + +Configure the following file system settings for MGN integration. @@ -181 +181 @@ MGN can work with an existing FSx for ONTAP file system or a new one. If you do - * **Storage capacity** : MGN uses FSx for ONTAP storage for replication, conversion, and cutover. These processes require temporary storage on the file system. Ensure that sufficient space is available on the FSx for ONTAP file system and increase capacity if needed. As a guideline, provision 3x the size of the planned migration data. The 3x factor accounts for three concurrent storage consumers during migration: the replicated data, the converted volumes used for launch, and the original volumes pending deletion. Volume deletion in FSx for ONTAP is a background operation, so freed capacity is not available immediately after deletion, so headroom must be provisioned upfront. As a best practice, keep the file system at or below 80% SSD capacity utilization throughout the migration. For second-generation file systems ([Single-AZ 2 and Multi-AZ 2](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/high-availability-AZ.html) deployment types), you can decrease storage capacity after migration is complete. For more information, see [Managing storage capacity and provisioned IOPS](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/storage-capacity-and-IOPS.html). + * **Storage capacity** : Migration can require up to three times the total provisioned capacity of all source disks that you migrate. The maximum applies when all of the following consumers exist at the same time: @@ -183 +183,5 @@ MGN can work with an existing FSx for ONTAP file system or a new one. If you do - * **Throughput capacity** : Higher throughput capacity reduces migration time. Throughput is selected from supported values and is a billable dimension. To size throughput for migration, sum the average read throughput and write throughput across all source servers being migrated to the file system, add 15% headroom, and round up to the next supported value. Plan your throughput capacity before starting migration, as changes take time to take effect. You can reduce throughput after migration is complete. For more information, see [Managing throughput capacity](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/managing-throughput-capacity.html) and [FSx for ONTAP performance](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/performance.html). + * Replication volumes for source servers that are still migrating + + * Target FlexClone volumes that MGN uses for launch + + * Volumes that are pending deletion. FSx for ONTAP frees their capacity in the background rather than immediately. @@ -184,0 +189 @@ MGN can work with an existing FSx for ONTAP file system or a new one. If you do +To avoid running out of capacity during migration, we recommend that you set the file system's SSD storage capacity to 3x the total provisioned capacity of your source disks before you start. You need this capacity only while the migration runs. On second-generation file systems ([Single-AZ 2 and Multi-AZ 2](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/high-availability-AZ.html)), you can decrease storage capacity after the migration is complete. To stay at or below 80% SSD capacity utilization, divide the result by 0.8. For example, for 10 TiB of source disks, set 30 TiB, or set 37.5 TiB to stay at or below 80% utilization. For more information about storage capacity, see [Managing storage capacity and provisioned IOPS](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/storage-capacity-and-IOPS.html). @@ -185,0 +191,3 @@ MGN can work with an existing FSx for ONTAP file system or a new one. If you do + * **Throughput capacity** : Higher throughput capacity reduces migration time. Throughput is selected from supported values and is a billable dimension. To size throughput for migration, sum the average read throughput and write throughput across all source servers being migrated to the file system, add 15% headroom, and round up to the next supported value. Plan your throughput capacity before starting migration, as changes take time to take effect. You can reduce throughput after migration is complete. For more information, see [Managing throughput capacity](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/managing-throughput-capacity.html) and [FSx for ONTAP performance](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/performance.html). + + * **Autonomous Ransomware Protection (ARP)** : If ONTAP ARP is enabled on the file system, disable it before migration. Otherwise, ARP can prevent MGN from deleting replication volumes. This happens during the Finalize cutover and Disconnect from service migration stages. For more information about ARP, see [Enabling Autonomous Ransomware Protection](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/enable-ARP.html). @@ -186,0 +195 @@ MGN can work with an existing FSx for ONTAP file system or a new one. If you do + * **Maintenance window** : FSx for ONTAP maintenance can interrupt replication and test and cutover launches. Before you start the migration, move the maintenance window outside your migration timeline. If the migration takes longer than 14 days, schedule the window for a time when you don't plan any launches. For more information, see [Optimizing performance with FSx for ONTAP maintenance windows](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/maintenance-windows.html). @@ -188 +196,0 @@ MGN can work with an existing FSx for ONTAP file system or a new one. If you do -###### Disable Autonomous Ransomware Protection (ARP) @@ -190 +197,0 @@ MGN can work with an existing FSx for ONTAP file system or a new one. If you do -If ONTAP ARP is enabled on the file system, disable it before migration. ARP can prevent MGN from deleting replication volumes on Finalize cutover/Disconnect from service migration stage. For more information, see [Enabling Autonomous Ransomware Protection](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/enable-ARP.html). @@ -192 +198,0 @@ If ONTAP ARP is enabled on the file system, disable it before migration. ARP can -For detailed instructions on creating and configuring FSx for ONTAP file systems, see [Creating FSx for ONTAP file systems](https://docs.aws.amazon.com/fsx/latest/ONTAPGuide/creating-file-systems.html). @@ -198,2 +203,0 @@ For detailed instructions on creating and configuring FSx for ONTAP file systems -###### Note - @@ -212,3 +216 @@ Certificate options Option | Use Case | Documentation -###### Note - -The private key must be in PKCS#8 format (`-----BEGIN PRIVATE KEY-----`). If your key starts with `-----BEGIN RSA PRIVATE KEY-----` (PKCS#1), convert it: +The private key must be in PKCS#8 format (`-----BEGIN PRIVATE KEY-----`). If your key starts with `-----BEGIN RSA PRIVATE KEY-----` (PKCS#1), use the following OpenSSL commands to convert it: @@ -283 +285 @@ Store the client certificate and private key in AWS Secrets Manager (Secrets Man -MGN expects the secret to contain exactly two keys: +MGN expects the secret to contain exactly two keys, with these exact names: @@ -291,0 +294,2 @@ MGN expects the secret to contain exactly two keys: +Don't use other key names, such as `certificate` or `private_key`, and don't add other keys, such as `username`. + @@ -317,11 +320,0 @@ MGN expects the secret to contain exactly two keys: -###### Important - - * Use `cert` (not `certificate`). - - * Use `key` (not `private_key`). - - * Do NOT include a `username` field. - - - - @@ -368,3 +361 @@ Changing the storage provider for a source server that is already replicating te -###### Note - -Migration Acceleration Program (MAP) 2.0 tags are applied to the FSx for ONTAP file system but not to individual FSx for ONTAP volumes. +Migration Acceleration Program (MAP) 2.0 tags apply to the FSx for ONTAP file system but not to individual FSx for ONTAP volumes.