AWS Storage Gateway User Guide
Supported Hypervisors and Host Requirements
3.amazon.pool.ntp.org
Depending on your gateway's AWS Region, replace
region
in the endpoint with the corresponding
region string. For example, if you create a gateway in the US West (Oregon) region, the endpoint looks
like this:
storagegateway.us-west-2.amazonaws.com:443
.
• Storage Gateway—For supported AWS Regions and a list of AWS service endpoints you can use with
Storage Gateway, see
AWS General Reference
.
• AWS Storage Gateway Hardware Appliance—For supported AWS Regions you can use with the
hardware appliance see
AWS Storage Gateway Hardware Appliance Regions
in the
AWS General
Reference
.
Configuring Security Groups for Your Amazon EC2 Gateway
Instance
A security group controls traffic to your Amazon EC2 gateway instance. When you create an instance
from the Amazon Machine Image (AMI) for AWS Storage Gateway from AWS Marketplace, you have two
choices for launching the instance. To launch the instance by using the
1-Click Launch
feature of AWS
Marketplace, follow the steps in
Deploying a Volume or Tape Gateway on an Amazon EC2 Host (p. 349)
. We recommend that you use this
1-Click Launch
feature.
You can also launch an instance by using the
Manual Launch
feature in AWS Marketplace. In this case,
an autogenerated security group that is named
AWS Storage Gateway-1-0-AutogenByAWSMP-
is created. This security group has the correct rule for port 80 to activate your gateway. For more
information about security groups, see
Amazon EC2 User Guide for Linux
Instances
.
Regardless of the security group that you use, we recommend the following:
• The security group should not allow incoming connections from the outside internet. It should allow
only instances within the gateway security group to communicate with the gateway. If you need to
allow instances to connect to the gateway from outside its security group, we recommend that you
allow connections only on ports 3260 (for iSCSI connections) and 80 (for activation).
• If you want to activate your gateway from an EC2 host outside the gateway security group, allow
incoming connections on port 80 from the IP address of that host. If you cannot determine the
activating host's IP address, you can open port 80, activate your gateway, and then close access on
port 80 after completing activation.
• Allow port 22 access only if you are using AWS Support for troubleshooting purposes. For more
You Want AWS Support to Help Troubleshoot Your EC2 Gateway (p. 325)
.
In some cases, you might use an Amazon EC2 instance as an initiator (that is, to connect to iSCSI targets
on a gateway that you deployed on Amazon EC2). In such a case, we recommend a two-step approach:
1. You should launch the initiator instance in the same security group as your gateway.
2. You should configure access so the initiator can communicate with your gateway.
For information about the ports to open for your gateway, see
Supported Hypervisors and Host Requirements
You can run AWS Storage Gateway on-premises as either a virtual machine (VM) appliance, or a physical
hardware appliance, or in AWS as an Amazon Elastic Compute Cloud (Amazon EC2) instance.
AWS Storage Gateway supports the following hypervisor versions and hosts:
API Version 2013-06-30
20