AWS filegateway documentation change
Summary
Added cost considerations for data migration and operational notes about VM activation/proxy configuration
Security assessment
Focuses on cost optimization and operational procedures without any security-related content or implications for vulnerabilities.
Diff
diff --git a/filegateway/latest/files3/migrate-data.md b/filegateway/latest/files3/migrate-data.md index 6da9f2bff..96fc5eea6 100644 --- a//filegateway/latest/files3/migrate-data.md +++ b//filegateway/latest/files3/migrate-data.md @@ -29,0 +30 @@ Writing to one Amazon S3 bucket from two file shares simultaneously is _not supp +**Cost implication** | Cached data preservation eliminates the need for re-downloads, resulting in zero additional S3 costs. | This method may incur additional costs, particularly if data retrieval from S3 is necessary. This approach can also result in substantial S3 data retrieval expenses if the file shares backed by S3 buckets utilize storage classes such as S3 Intelligent-Tiering, S3 Standard-IA, S3 One Zone-IA, or objects transitioned to GLACIER through S3 lifecycle policies. In the case of SMB file shares, if the root ACL is configured on the file share, it must be re-applied to the migrated gateway. This action will apply the setting recursively to all objects within the file share, introducing some cost implications. @@ -74,0 +76,4 @@ Do not add cache disks for the new VM. This VM will use the same cache disks tha +###### Note + +After downloading the VM, close the console wizard. Do not proceed with activation at this point. + @@ -82,0 +88,4 @@ If your gateway VM must use a Socket Secure version 5 (SOCKS5) proxy to connect +###### Note + +You can reuse the same static IP address or hostname from the old gateway VM to avoid reconfiguring NFS or SMB clients. +