Setup an AWS Gateway to access Amazon S3 objects
If the used backup software doesn't support a direct access to Amazon S3, you need to configure an AWS Gateway in your infrastructure to access the S3 objects in AWS environment.
An AWS Gateway is basically an appliance available in different platforms (VMware, Hyper-V, Amazon EC2) that connects an on-premises software appliance with cloud-based storage.
AWS Gateway configuration
Login to the AWS Management Console and select the Storage Gateway option under Storage area. File gateway enables you to store and retrieve objects in Amazon S3 using industry-standard file protocols such as Network File System (NFS).
Click Get started to begin the AWS Storage Gateway configuration.
From the Select gateway type tab, select File gateway and click Next.
Select the host platform to use (in the example VMware ESXi) and click on Download image button.
Click Next when download has been completed. Before proceeding with next step, we need to deploy and configure the AWS gateway appliance in the virtual infrastructure.
Deploy the AWS Gateway
Open the vSphere Web Client, right click the cluster and select Deploy OVF Template option.
Click Browse in the wizard to select the .OVF file to use then click Next.
Enter a Name and specify a location. Click Next.
Select a resource where to run the appliance and click Next.
Click Next to continue.
Select the virtual disk format and the storage then click Next.
Select the correct Destination Network and click Next.
Click Finish to start the deployment.
Configure the AWS Gateway appliance
Once the appliance installation has completed, right click the VM and select Edit Settings.
Go to VM Options tab, expand VMware Tools and enable the Synchronize guest time with host option.
Since file gateways require at least one dedicated disk as a cache storage, go to Virtual Hardware tab and add a new Hard Disk device. Cache storage acts as the on-premises durable store for data that is waiting to upload to Amazon S3. You should allocate at least 20% of your existing file store size as cache storage and it is recommended to have a disk size of at least 150 GB.
Add a new SCSI Controller and set the type as VMware Paravirtual. Assign the SCSI Controller to the created new hard disk. Click OK to save the configuration.
Right click the AWS Gateway appliance and select Power > Power On option.
Access the appliance console in order to configure the network parameters.
Enter the default credentials sguser/sgpassword to login.
Enter number 2 to configure network parameters and press Enter.
Enter number 3 to configure static IP and press Enter.
Enter all the required parameters then type y to apply the configuration.
Press Return to continue.
Enter x to complete the configuration.
Configuration has updated in the system. Press Return to continue.
The AWS Gateway appliance configuration has been completed successfully. Enter x to exit the session.
Resume AWS configuration
When the appliance IP address has been configured, go back to the AWS Management Console to complete the setup of the gateway. Enter the configured IP address and click on Connect to gateway button.
Specify the Gateway name and click Activate gateway.
Once the gateway has been activated, choose the disk used for the cache then click Save and Continue.
The AWS Gateway has been configured successfully. Next step is the creation of a S3 Bucket required to create a file share.
Create an Amazon S3 Bucket
From the AWS Management Console, select S3 under Storage area.
Click the + Create bucket button.
Specify the Bucket name and the Region then click Next.
If you don't need to activate specific features, click Next to continue.
Make sure your account has read and write permissions then click Next.
Double check entered configuration and click Create bucket.
The new Bucket has been created.
Create a file share
When a S3 Bucket is available to use, go back to the Storage Gateway configuration page and click Create file share.
Enter the Amazon S3 bucket name and leave default options. Click Next.
At the Review window, double check the default values:
- Allowed clients: the default value to 0.0.0.0/0 to allow the access from any IP. For security reasons, it is recommended to change this configuration.
- Squash level: by default, this parameter is set to Root squash. Double check the requirements for the used software.
Click Create file share to save the configuration.
The file share has been created successfully.
The AWS environment is now configured to use Amazon S3 as offsite storage or, for example, as external backup repository.
