AWS Storage Gateway User Guide
Creating a Gateway Using a VPC Endpoint
3. Choose
Next
to connect to your gateway and activate your gateway.
Connect to Your Gateway
To connect to your gateway, the first step is to get the IP address of your gateway VM. You use this IP
address to activate your gateway. For gateways deployed and activated on an on-premises host, you can
get the IP address from your gateway VM local console or your hypervisor client. For gateways deployed
and activated on an Amazon EC2 instance, you can get the IP address from the Amazon EC2 console.
The activation process associates your gateway with your AWS account. Your gateway VM must be
running for activation to succeed.
Make sure that you select the correct gateway type. The .ova files and AMIs for the gateway types are
different and are not interchangeable.
To get the IP address for your gateway VM from the local console
1. Log on to your gateway VM local console. For detailed instructions, see the following:
• VMware ESXi—
Accessing the Gateway Local Console with VMware ESXi (p. 273)
.
• Microsoft Hyper-V—
Access the Gateway Local Console with Microsoft Hyper-V (p. 274)
2. Get the IP address from the top of the menu page, and make note of it for later use.
To get the IP address from an EC2 instance
1. Open the Amazon EC2 console at
https://console.amazonaws.cn/ec2/
.
2. In the navigation pane, choose
Instances
, and then choose the EC2 instance.
3. Choose the
Description
tab at the bottom, and then note the IP address. You use this IP address to
activate the gateway.
For activation, you can use the public or private IP address assigned to a gateway. You must be able
to reach the IP address that you use from the browser from which you perform the activation. In this
walkthrough, we use the public IP address to activate the gateway.
Setup and Configure a HTTP Proxy (On-premises File Gateway Only)
If you are activating a file gateway, you need to setup a http proxy and configure it in the file gateway
VM local console. This proxy is needed for on-premises file gateway to access Amazon S3 private
endpoints from outside your VPC. If you already have a http proxy in Amazon EC2, you can use it. You do,
however, need to verify that all of the following TCP ports are allowed in your security group:
• TCP 443
• TCP 1026
• TCP 1027
• TCP 1028
API Version 2013-06-30
138