This tutorial will show you how to start TigerGraph Enterprise Edition from an image on AWS.
1. Go to AWS Marketplace and search for TigerGraph. 2. Click "Continue to Subscribe".
3. Click on "Continue to Configuration".
4. Select the Software Version and Region. We recommend selecting the latest version for the most up-to-date features. After making your selections, click on "Continue to Launch".
5. Select the instance type, security group settings, and other settings. The default settings are fine for most users, but feel free to modify them. Click "Launch" when finished. Notes: The instance type needs to have at least 4 CPUs and 16GB RAM for TigerGraph to work properly. The security group must allow inbound TCP traffic to port 14240 if you want to access GraphStudio (TigerGraph's visualization platform). For more about GraphStudio, see the GraphStudio UI Guide. The security group must allow inbound TCP traffic to port 9000 if you want to send RESTful requests to TigerGraph from outside the instance (this includes configuring the GSQL client on a remote machine). For more about the REST API, see the TigerGraph RESTful API User Guide.
For more about the TigerGraph Platform, see the TigerGraph Platform Overview.
6. That's it! The TigerGraph instance has been successfully deployed on AWS.
Log on to the instance and switch to user
tigergraph using the following command:
sudo su - tigergraph
2. Run the following command to check the current status of TigerGraph. The services "ADMIN", "CTRL", "ETCD", "IFM", "KAFKA", and "ZK" are started automatically and should be up at this point. If any of them are not or you get the following error message, please wait for 30 to 60 seconds and check the status again before reporting it to TigerGraph support.
3. Run the following command to start TigerGraph:
4. Check the status again. All services should be up at this point:
5. TigerGraph has been successfully started on your cloud instance.
The TigerGraph Enterprise edition image comes with a perpetual license that will only work on the AWS instance it's installed on. Please run the following command to see it:
gadmin license status