Skip to main content

Check out Interactive Visual Stories to gain hands-on experience with the SSE product features. Click here.

Skyhigh Security

AWS Requirements

When installing Secure Web Gateway as a virtual machine (VM) that runs as an instance in an Amazon Web Services (AWS) environment, you must have information about several environment parameters available.

You must also choose an AWS instance type, depending on how you want to use Secure Web Gateway.

AWS Environment Parameters

An AWS environment can be described by specifying its parameters, for example, its region or account numbers. Be sure to have the following information available before the installation:

  • AMI ID — ID for an instance of Secure Web Gateway that you want to set up in an AWS environment.

    This ID is displayed on the AWS console that is used for the setup when the instance is ready for launching. By comparing the displayed number with the number in a list, you can verify that this is the instance you want to launch.

  • Region — Region where you want to run an instance

    The instance ID changes for an instance when it is run in different regions. The mapping of IDs to regions can also be looked up in the list mentioned above.

  • AWS account number — Number of the AWSs account that is owned by Skyhigh Security

    The account number is also displayed on the AWS console when an instance is ready for launching.

For the list of valid AMI IDs and regions, as well as for the account number, see the download section of the Skyhigh Security Content & Cloud Security Portal at

Choose an AWS Instance Type

Before installing Secure Web Gateway as an instance in an AWS environment, you must choose an AWS instance type.

For Secure Web Gateway, only AWS instance types that belong to the HVM type group are supported.

Which instance type you choose depends on what you want to use a Secure Web Gateway instance for, for example, testing or production. You should also take into account network performance.

Once you have chosen an AWS instance type for a Secure Web Gateway instance and installed this instance, you must keep it. You cannot change the AWS instance type later on.

Use Cases and AWS Instance Types

The following table shows some common use cases and AWS instance types that you can choose.

Web caching is not included among the features of Secure Web Gateway when run as an instance in an AWS environment, which reduces the requirements for available hard-disk space.

Use RAM (in GB) Hard-disk space (in GB) CPU cores AWS instance type
Functional testing (user interface based on Java applet or desktop client) 4 80 4 m4.large
Functional testing (HTML-based user interface) 8 80 4 m4.large
Production (minimum) 16 80 4 m4.xlarge
Production (recommended) 32 or more 80 or more 4 or more m4.2xlarge


  • Was this article helpful?