Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
storagegateway_gateway_fault_tolerantProvider: AWS
Service:
storagegatewaySeverity: MEDIUM
Categories:
resilienceResource type:
OtherWhat this check verifies
AWS Storage Gateway hosted on an EC2 instance is flagged by assessing each gateway’s hosting environment, distinguishing single-instance EC2 deployments from non-EC2 platforms that can leverage platform-level high availability.Risk
A single EC2-hosted gateway concentrates failure risk. Instance or AZ disruption, reboots, or network faults can halt file access, causing downtime and stalled writes. This degrades availability and can affect integrity via partial operations or cache desynchronization.Recommendation
Design for high availability: avoid single-instance gateways for critical workloads. Prefer managed multi-AZ services like EFS or FSx, or use multiple gateways with client failover and resilient naming. Apply defense in depth, validate failover regularly, and monitor health to prevent outages.Remediation
Dashboard steps- In the AWS Console, go to Storage Gateway and click Create gateway
- Choose your gateway type, then under Host platform select VMware ESXi, Microsoft Hyper-V, Linux KVM, or Hardware Appliance (do not select Amazon EC2)
- Download and deploy the VM on your host, power it on, and note its IP
- In the console, connect to and Activate the new gateway
- Recreate equivalent resources (shares/volumes/tapes) on the new gateway and update clients to use the new gateway IP/DNS
- In Storage Gateway > Gateways, delete the old EC2-hosted gateway
- Verify the new gateway’s details show Host platform not equal to Amazon EC2
References
- https://docs.aws.amazon.com/filegateway/latest/files3/resource-vm-setup.html
- https://docs.aws.amazon.com/filegateway/latest/files3/disaster-recovery-resiliency.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = storagegateway_gateway_fault_tolerant. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks