AWS Storage Gateway User Guide
Hardware and Storage Requirements
Topics
•
Hardware and Storage Requirements (p. 11)
•
Network and Firewall Requirements (p. 12)
•
Supported Hypervisors and Host Requirements (p. 20)
•
Supported NFS Clients for a File Gateway (p. 21)
•
Supported SMB Clients for a File Gateway (p. 21)
•
Supported File System Operations for a File Gateway (p. 21)
•
Supported iSCSI Initiators (p. 22)
•
Supported Third-Party Backup Applications for a Tape Gateway (p. 22)
Hardware and Storage Requirements
In this section, you can find information about the minimum hardware and settings for your gateway
and the minimum amount of disk space to allocate for the required storage. For information about best
practices for file gateway performance, see
Performance Guidance for File Gateways (p. 285)
.
Hardware Requirements for On-Premises VMs
When deploying your gateway on-premises, you must make sure that the underlying hardware on which
you deploy the gateway VM can dedicate the following minimum resources:
• Four virtual processors assigned to the VM.
• 16 GiB of reserved RAM assigned to the VM.
• 80 GiB of disk space for installation of VM image and system data.
For more information, see
Optimizing Gateway Performance (p. 287)
. For information about how your
hardware affects the performance of the gateway VM, see
AWS Storage Gateway Limits (p. 395)
Requirements for Amazon EC2 Instance Types
When deploying your gateway on Amazon EC2, the instance size must be at least
xlarge
for your
gateway to function. However, for the compute-optimized instance family the size must be at least
2xlarge
. Use one of the following instance types recommended for your gateway type.
Recommended for file gateway types
• General-purpose instance family— m4 or m5 instance type.
• Compute-optimized instance family— c4 or c5 instance types. Select the
2xlarge
instance size or
higher to meet the required RAM requirements.
• Memory-optimized instance family—r3 instance types.
• Storage-optimized instance family— i3 instance types.
Note
When you launch your gateway in EC2, and the instance type you’ve selected supports
ephemeral storage, the disks will be listed automatically. To learn more about Amazon EC2
. Note that application writes are stored in the cache synchronously,
and then asynchronously uploaded to durable storage in Amazon S3. If the ephemeral
storage is lost because an instance stops before the upload is complete, then the data that
still resides in cache and has not yet written to S3 can be lost. Before you stop the instance
that hosts the gateway make sure the CachePercentDirty CloudWatch metric is
0
. For more
information about monitoring metrics for your storage gateway, see
API Version 2013-06-30
11