AWS storagegateway documentation change
Summary
Added a Pre-migration Checklist section with requirements including using latest gateway images, matching hardware configurations, verifying disk sizing, applying software updates, and testing network connectivity
Security assessment
The changes focus on migration best practices and operational readiness. While applying software updates may include security patches, there is no explicit mention of security vulnerabilities, exploits, or security-specific features.
Diff
diff --git a/storagegateway/latest/tgw/al2-to-al2023-migration.md b/storagegateway/latest/tgw/al2-to-al2023-migration.md index 4ff1f28f7..d5367de2e 100644 --- a//storagegateway/latest/tgw/al2-to-al2023-migration.md +++ b//storagegateway/latest/tgw/al2-to-al2023-migration.md @@ -43,0 +44,27 @@ The migration timeline includes several critical milestones: +### Pre-migration Checklist + +###### Important + +Before beginning the migration process, verify the following requirements to ensure a successful migration. + + * **Use the latest gateway image.** When creating the new Storage Gateway VM: + + * For Amazon EC2 gateways, use the latest AMI from the public SSM parameter or use the Storage Gateway console. + + * For on-premises gateways, download the latest VM image from the Storage Gateway console. + + * **Match the hardware configuration.** Ensure the new gateway VM uses the same CPU, memory, and network throughput as the existing gateway. For EC2 gateways, use the same instance type. + + * **Verify root disk sizing.** The new gateway VM's root disk must be at least the same size as the existing gateway's root disk. If the existing root disk has less than 20 GB of available space, size the new root disk to: (existing root disk size) + (20 GB minus available space on existing root disk). + + * **Apply pending software updates.** Before starting migration, apply any pending software updates on the existing gateway. Open the **Storage Gateway** console, select your gateway, and choose **Update Now** if available. + + * **Verify network connectivity from the new gateway.** Before initiating migration, confirm that the new gateway VM can reach: + + * Storage Gateway service endpoints (or your VPC endpoints). + + * Use the gateway local console's network connectivity test to validate all endpoints pass. + + + +