You don't need to be concerned with the usage of the Cache disk as File Gateway will evict the oldest files when the Cache disk usage nears 100%. As the name says, "Cache" disk is used to cache the most recently used files from your S3 bucket. Your "Cache" disk size can be much smaller than the size of your S3 bucket.
In summary, you don't need to worry about the Cache disk usage as long as your Cache dirty% remains small. If your data set grows to a point where Cache dirty% remains high for long time periods, you can consider increasing the Cache disk size by adding additional cache disks.
Ok, It is just that we store under 100Gb, but the cache uses 900Gb....However the usage seems to have leveled out at 90% full now and does not increase
What is the difference between extentions and powertools when fetching in cache from parameter store?asked a month ago
Does the file gateway cache need to be at least as large as the largest file being uploaded?Accepted Answerasked 3 years ago
How does API Gateway encrypt its cache?asked a year ago
Can I use API Gateway cache invalidation with a custom authorizer ?asked 10 months ago
Storage Gateway File Gateway local cache file systemAccepted Answerasked 3 months ago
S3 updated, but NFS share on the file gateway is notasked 4 years ago
Only allow specific Roles to invalidate API Gateway Cacheasked 3 months ago
File gateway Cache fills upasked 3 years ago
Manage FSx Storage Gateway CacheAccepted Answerasked a month ago
File Storage Gateway - Maximum allowable cache size?asked 3 years ago