AWS storagegateway documentation change
Summary
Updated migration procedure for cached Volume Gateways with added steps for gateway version updates, CachePercentDirty verification, and refined disk attachment/migration instructions. Changed note to important warning about version compatibility.
Security assessment
The changes focus on procedural improvements and version compatibility clarifications. While updating gateways to latest versions (step 2) is a security best practice, there is no explicit mention of addressing vulnerabilities or security incidents. The CachePercentDirty check ensures data consistency but does not directly relate to security controls.
Diff
diff --git a/storagegateway/latest/vgw/migrate-data.md b/storagegateway/latest/vgw/migrate-data.md index 9c4eb53fc..58fe341a4 100644 --- a//storagegateway/latest/vgw/migrate-data.md +++ b//storagegateway/latest/vgw/migrate-data.md @@ -20 +20 @@ The steps that you follow to move your data to a new gateway depend on the gatew -###### Note +###### Important @@ -24 +24 @@ Data can only be moved between the same gateway types. -The following migration instructions can only be used for gateway appliances version 2.x or lower. You can't use them to migrate to version 3.x or higher. +The following migration instructions can only be used for gateway appliances running version 2.x. You can't use them to migrate gateway appliances running lower versions. @@ -109 +109,7 @@ When a gateway is deleted, there is no way to recover it. - 2. Unmount or disconnect iSCSI volumes from any clients that are using them. This helps keep data on those volumes consistent by preventing clients from changing or adding data to those volumes. + 2. Use the following steps to update the gateway to the latest version + + 1. Open the Storage Gateway console at [https://console.aws.amazon.com/storagegateway/home](https://console.aws.amazon.com/storagegateway/). + + 2. In the navigation pane, choose **Gateways** , and then choose the old cached Volume Gateway that you want to migrate. + + 3. Click **Update Now** if available. If not, your gateway is already on the latest version. @@ -111 +117,5 @@ When a gateway is deleted, there is no way to recover it. - 3. Use the following steps to create a snapshot of your volume, and then wait for the snapshot to complete. + 3. Verify that the `CachePercentDirty` metric on the **Monitoring** tab for the existing Cached Gateway is `0`. + + 4. Unmount or disconnect iSCSI volumes from any clients that are using them. This helps keep data on those volumes consistent by preventing clients from changing or adding data to those volumes. + + 5. Use the following steps to create a snapshot of your volume, and then wait for the snapshot to complete. @@ -117 +127 @@ When a gateway is deleted, there is no way to recover it. - 3. For **Actions** , choose **Create snapshot**. + 3. For **Actions** , choose **Create EBS snapshot**. @@ -125 +135 @@ For more information about checking volume status in the console, see [Understan - 4. Use the following steps to stop the old cached Volume Gateway: + 6. Use the following steps to stop the old cached Volume Gateway: @@ -127 +137 @@ For more information about checking volume status in the console, see [Understan - 1. In the navigation pane, choose **Gateways** , and then choose the old cached Volume Gateway that you want to stop. The status of the gateway is **Running**. + 1. In the navigation pane, choose **Gateways** , and then choose the old cached Volume Gateway that you want to stop. @@ -137 +147 @@ For more information about stopping a gateway, see [Starting and Stopping a Volu - 5. Detach all disks, including the root disk, cache disks, and upload buffer disks, from the old gateway VM. + 7. Detach all disks, including the root disk, cache disks, and upload buffer disks, from the old gateway VM. @@ -141 +151 @@ For more information about stopping a gateway, see [Starting and Stopping a Volu -Make a note of the root disk's volume ID, as well as the gateway ID associated with that root disk. You detach this disk from the new Storage Gateway hypervisor in a later step. (See step 11.) +Make a note of the root disk's volume ID, as well as the gateway ID associated with that root disk. You use this disk in later steps. @@ -145 +155 @@ If you are using an Amazon EC2 instance as the VM for your cached Volume Gateway - 6. Create a new Storage Gateway hypervisor VM instance, but don't activate it as a gateway. For more information about creating a new Storage Gateway hypervisor VM, see [Set up a Volume Gateway](./create-volume-gateway.html#set-up-gateway-volume). This new gateway will assume the identity of the old gateway. + 8. Create a new Storage Gateway hypervisor VM instance, but don't activate it as a gateway. For more information about creating a new Storage Gateway hypervisor VM, see [Set up a Volume Gateway](./create-volume-gateway.html#set-up-gateway-volume). This new gateway will assume the identity of the old gateway. @@ -151 +161 @@ Do not add disks for cache or upload buffer to the new VM. Your new VM will use - 7. Your new Storage Gateway hypervisor VM instance should use the same network configuration as the old VM. The default network configuration for the gateway is Dynamic Host Configuration Protocol (DHCP). With DHCP, your gateway is automatically assigned an IP address. + 9. Your new Storage Gateway hypervisor VM instance should use the same network configuration as the old VM. The default network configuration for the gateway is Dynamic Host Configuration Protocol (DHCP). With DHCP, your gateway is automatically assigned an IP address. @@ -155 +165 @@ If you need to manually configure a static IP address for your new VM, see [Conf - 8. Start the new VM. + 10. Start the new VM. @@ -157 +167 @@ If you need to manually configure a static IP address for your new VM, see [Conf - 9. Attach the disks that you detached from the old cached Volume Gateway VM in step 5, to the new cached Volume Gateway. Attach them in the same order to the new gateway VM as they are on the old gateway VM. + 11. Attach the disks that you detached from the old cached Volume Gateway VM in step 7, to the new cached Volume Gateway. Attach them in the same order to the new gateway VM as they are on the old gateway VM. @@ -161 +171,5 @@ All disks must make the transition unchanged. Do not change volume sizes, as tha - 10. Initiate the gateway migration process by connecting to the new VM with a URL that uses the following format. + 12. Initiate the gateway migration process by either connecting to the new gateway VM’s local console, or making web requests to the new gateway VM's IP address (described below). + + 1. To use the local console, select the option for **Migrate Gateway** and provide your existing gateway ID when prompted. You will be provided prompts to copy previously applied settings on old gateway to the new gateway. You may choose to apply them or manually configure them later. See [Accessing the Gateway Local Console](https://docs.aws.amazon.com/storagegateway/latest/vgw/accessing-local-console.html). + + 2. Alternatively, you can initiate the gateway migration process by connecting to the new VM with a URL that uses the following format. @@ -171,3 +185 @@ Use this URL from a browser, or from the command line using `curl`, to initiate -When the gateway migration process is successfully initiated, you will see the following message: - -`Successfully imported Storage Gateway information. Please refer to Storage Gateway documentation to perform the next steps to complete the migration.` +When the gateway migration process is successfully completed, you will see a message confirming successful migration. @@ -175 +187 @@ When the gateway migration process is successfully initiated, you will see the f - 11. Detach the old gateway's root disk, whose volume ID you noted in step 5. + 13. Detach the old gateway's root disk, whose volume ID you noted in step 7. @@ -177 +189 @@ When the gateway migration process is successfully initiated, you will see the f - 12. Start the gateway. + 14. Start the gateway. @@ -189 +201 @@ For more information about starting a gateway, see [Starting and Stopping a Volu - 13. Your volumes should now be available to your applications at the new gateway VM's IP address. + 15. Your volumes should now be available to your applications through the new gateway VM's network interfaces. The migration success message includes details about the updated mapping between each volume and the new gateway’s network interface. For more information about the IP address associated with each network interface, visit the main page of the gateway’s local console. See [Accessing the Gateway Local Console](https://docs.aws.amazon.com/storagegateway/latest/vgw/accessing-local-console.html). @@ -191 +203 @@ For more information about starting a gateway, see [Starting and Stopping a Volu - 14. Confirm that your volumes are available, and delete the old gateway VM. For information about deleting a VM, see the documentation for your hypervisor. + 16. Confirm that your volumes are available, and delete the old gateway VM. For information about deleting a VM, see the documentation for your hypervisor.