AWS Storage Gateway User Guide
Recommended Local Disk Sizes For Your Gateway
Description
Tape Gateway
Total size of all tapes in a virtual tape library (VTL) 1 PiB
Maximum number of virtual tapes in archive
No limit
Total size of all tapes in a archive
No limit
Recommended Local Disk Sizes For Your Gateway
The following table recommends sizes for local disk storage for your deployed gateway.
Gateway Type
Cache
(Minimum)
Cache
(Maximum)
Upload Buffer
(Minimum)
Upload Buffer
(Maximum)
Other
Required Local
Disks
File gateway
150 GiB
16 TiB
—
—
—
Cached volume
gateway
150 GiB
16 TiB
150 GiB
2 TiB
—
Stored volume
gateway
—
—
150 GiB
2 TiB
1 or more for
stored volume
or volumes
Tape gateway
150 GiB
16 TiB
150 GiB
2 TiB
—
Note
You can configure one or more local drives for your cache and upload buffer, up to the
maximum capacity.
When adding cache or upload buffer to an existing gateway, it's important to create new disks
in your host (hypervisor or Amazon EC2 instance). Don't change the size of existing disks if the
disks have been previously allocated as either a cache or upload buffer.
Using Storage Classes
AWS Storage Gateway supports the Amazon S3 Standard, Amazon S3 Standard-Infrequent Access,
Amazon S3 One Zone-Infrequent Access and Glacier storage classes. For more information about storage
classes, see
in the
Amazon Simple Storage Service Developer Guide
.
Using Infrequent Access Storage Class With File
Gateway
When you create or update a file share, you have the option to select a storage class for your objects.
You can either choose the Amazon S3 Standard or any of the infrequent access storage classes such as
S3 Standard IA or S3 One Zone IA. Objects stored in any of these storage classes can be transitioned to
GLACIER using a Lifecycle Policy.
Although you can write object directly from a file share to the S3-Standard-IA or S3-One Zone-IA storage
class, we recommend you use a Lifecycle Policy to transition your objects rather than write directly from
the file share, especially if you're expecting to update or delete the object within 30 days of archiving it.
For information about Lifecycle Policy, see
.
API Version 2013-06-30
397