Launch a Service Gateway virtual appliance from Amazon Web Services using Amazon Machine Images.
If you do not have VMware or Microsoft Hyper-V in your environment, you can deploy the Service Gateway virtual appliance from Amazon Web Services (AWS) using Amazon Machine Images (AMI). Before you begin, review the Service Gateway Appliance System Requirements to ensure your virtual appliance has the settings needed to deploy the services you want to use.
The steps contained in these instructions are valid as of April 2023.
The registration token is used to register the Service Gateway virtual appliance to Service Gateway Inventory after installation and setup are complete. The registration token expires after 24 hours if not used.
You must use an account that has permission to access the EC2 service.
If you don't see the EC2 service, use the search bar at the top of the screen to search for EC2. Find EC2 under Services.
The region can be set to any region you require the Service Gateway to be deployed. If you are unsure which region to select, use the default region for your AWS account.
The Launch an instance screen appears.
Adding tags helps with managing virtual machines by providing a way to track ownership or locate resources associated with deployed instances.
The default instance is C3.2xlarge with 8 vCPU and 15 GiB memory.
Service Gateway supports the following recommended instance types. Select the one best suited for your needs.
C3.xlarge
C3.2xlarge
C3.4xlarge
For more information, see Service Gateway Appliance System Requirements.
Trend Micro recommends accessing the Service Gateway virtual machine using an SSH client. Use the following settings for your key pair to enable SSH access:
Key pair type: RSA
Private key file format: .PEM
Select the VPC to use for the instance.
Select a Subnet that you want to use.
Set the Auto-assign Public IP to Disable.
For more information on how to set up a VPC and subnet, refer to the Amazon documentation .
Do not select "No preference" for the subnet.
AWS may automatically fill in the firewall settings and Inbound security groups rules. However, the settings may be incomplete. Review the settings and configure as needed.
Specify the Security group name.
Provide a Description of the security group.
Add Security group rules for each of the required Service Gateway ports.
Type |
Protocol |
Port Range |
Source Type |
Source |
Purpose |
---|---|---|---|---|---|
SSH |
TCP |
22 |
Recommended: Custom |
For accessing Service Gateway virtual appliance CLISH command |
|
HTTP |
TCP |
80 |
Recommended: Custom |
Service enabled queries for on-premises Active Directory servers, connected Trend Micro products (such as endpoint agents), Predictive Machine Learning, File Reputation Services, or Third-Party Integration |
|
HTTPS |
TCP |
443 |
Recommended: Custom |
Service enabled queries for on-premises Active Directory servers, connected Trend Micro products (such as endpoint agents), Predictive Machine Learning, File Reputation Services, or Third-Party Integration |
|
Custom TCP |
TCP |
5274 |
Recommended: Custom |
Web Reputation Services or Web Inspection Service queries |
|
Custom TCP |
TCP |
5275 |
Recommended: Custom |
Web Reputation Services or Web Inspection Service queries |
|
Custom TCP |
TCP |
8080 |
Recommended: Custom |
Forward Proxy Service listening port for connection |
|
Custom TCP |
TCP |
8088 |
Recommended: Custom |
Zero Trust Secure Access On-Premises Gateway listening port for connection |
Source type controls which IP addresses are allowed to connect to the Service Gateway virtual appliance. Trend Micro suggests setting Source type to Custom, then specifying Source IP addresses or security groups.
See the AWS help for more information about assigning IP addresses and security groups.
Trend Micro recommends using default settings for outbound port rules. Setting additional outbound rules may affect the ability of Service Gateway to connect to Service Gateway Inventory.
The minimum size for a volume is 200 GiB. If you need to extend the storage, you can increase the size of the volume or click Add new volume to add a disk.
Once you launch the instance, the Service Gateway virtual appliance begins installation. Installation may take a few minutes to complete. You can view the status of the instance in the EC2 console by going to Instances > Instances.
The Service Gateway virtual appliance is ready to connect and configure when the Instance state is Running and the Status check shows 2/2 checks passed.
Trend Micro recommends using an SSH client to connect to the Service Gateway virtual appliance to make copying the registration token easier. The following steps outline how to connect with an SSH client.
ssh -i "<keypair.pem>" admin@<IPaddress>
Use the full file name of your key pair including the file extension.
The user name is admin.
Use the Private IP address copied from AWS.
For example, if your key pair file is named my_key_pair.pem and the Private IP address is 127.0.0.1, type the command:
ssh -i "my_key_pair.pem" admin@127.0.0.1
If you are unable to immediately connect to the appliance, follow these steps to resolve the issue:
If you created a new key pair, EC2 may take some time to sync with the new key pair. Wait five minutes and try again.
The trusted hosts file cannot be automatically updated from EC2. In your SSH client, type the command ~/.ssh/known_hosts to remove the known hosts in the trusted file, then try connecting again.
The command prompt changes from from > to #.
register <registration_token>
Use the registration token you obtained from Service Gateway Inventory.
For more information on available commands, see Service Gateway CLI Commands.