AWS filegateway documentation change
Summary
Replaced 'Security' section header with 'Optimizing S3 File Gateway for SQL Server database backups' and removed redundant 'the' in a sentence.
Security assessment
Similar to the FSx File Gateway change, this removes a generic security section without adding new security documentation or addressing vulnerabilities.
Diff
diff --git a/filegateway/latest/files3/Performance-Throughput.md b/filegateway/latest/files3/Performance-Throughput.md index c8ef6b466..66b6eaecc 100644 --- a//filegateway/latest/files3/Performance-Throughput.md +++ b//filegateway/latest/files3/Performance-Throughput.md @@ -9 +9 @@ Deploy your gateway in the same location as your clientsReduce bottlenecks cause -The the following sections describe best practices for maximizing throughput between your NFS and SMB clients, S3 File Gateway, and Amazon S3. The guidance provided in each section contributes incrementally to improving overall throughput. While none of these recommendations are required, and they are not interdependent, they have been selected and ordered in a logical way that Support uses to test and tune S3 File Gateway implementations. As you implement and test these suggestions, keep in mind that each S3 File Gateway deployment is unique, so your results may vary. +The following sections describe best practices for maximizing throughput between your NFS and SMB clients, S3 File Gateway, and Amazon S3. The guidance provided in each section contributes incrementally to improving overall throughput. While none of these recommendations are required, and they are not interdependent, they have been selected and ordered in a logical way that Support uses to test and tune S3 File Gateway implementations. As you implement and test these suggestions, keep in mind that each S3 File Gateway deployment is unique, so your results may vary. @@ -288 +288 @@ Performance and optimization -Security +Optimizing S3 File Gateway for SQL Server database backups