AWS Storage Gateway User Guide
You Created an Amazon EBS Volume But
Can't Attach it to Your EC2 Gateway Instance
You Created an Amazon EBS Volume But Can't Attach
it to Your EC2 Gateway Instance
Check that the Amazon EBS volume in question is in the same Availability Zone as the gateway instance.
If there is a discrepancy in Availability Zones, create a new Amazon EBS volume in the same Availability
Zone as your instance.
You Can't Attach an Initiator to a Volume Target of
Your EC2 Gateway
Check that the security group that you launched the instance with includes a rule that allows the port
that you are using for iSCSI access. The port is usually set as 3260. For more information on connecting
Connecting to Your Volumes to a Windows Client (p. 365)
You Get a Message That You Have No Disks Available
When You Try to Add Storage Volumes
For a newly activated gateway, no volume storage is defined. Before you can define volume storage, you
must allocate local disks to the gateway to use as an upload buffer and cache storage. For a gateway
deployed to Amazon EC2, the local disks are Amazon EBS volumes attached to the instance. This error
message likely occurs because no Amazon EBS volumes are defined for the instance.
Check block devices defined for the instance that is running the gateway. If there are only two block
devices (the default devices that come with the AMI), then you should add storage. For more information
Deploying a Volume or Tape Gateway on an Amazon EC2 Host (p. 349)
. After attaching
two or more Amazon EBS volumes, try creating volume storage on the gateway.
You Want to Remove a Disk Allocated as Upload
Buffer Space to Reduce Upload Buffer Space
Follow the steps in
Determining the Size of Upload Buffer to Allocate (p. 221)
.
Throughput to or from Your EC2 Gateway Drops to
Zero
Verify that the gateway instance is running. If the instance is starting due to a reboot, for example, wait
for the instance to restart.
Also, verify that the gateway IP has not changed. If the instance was stopped and then restarted, the IP
address of the instance might have changed. In this case, you need to activate a new gateway.
You can view the throughput to and from your gateway from the Amazon CloudWatch console. For more
information about measuring throughput to and from your gateway to AWS, see
Between Your Gateway and AWS (p. 207)
You Want Your File Gateway to Use a C5 or M5 EC2
Instance Type Instead of C4 or M4
Do the following:
API Version 2013-06-30
324