In this document we describe how to launch an Amazon EC2 cloud instance with Navixy GPS tracking software. In fact it’s very easy because we offer Amazon Machine Image (AMI), which you can find in the AWS Marketplace.
Create an EC2 instance with Navixy application
Login to AWS Management Console with your credentials and choose EC2 instance
Click on the button “Launch instance”
Choose the “AWS marketplace” in the left menu and search for “Navixy”. Then choose the version you are need – Provider (if you want to offer GPS tracking services to other users) or Enterprise (if it’s only for your own company’s purposes).
Choose an appropriate instance type you need.
Below are our recommendations for the instance type depending on the amount of assets you’ll actively track.
If you want to become more acquainted with Navixy Cloud, there is no need to spend money at all. Start with AWS t2.micro instance type, which Amazon provides free of charge (AWS Free Tier). It is enough to deploy your Navixy Cloud and run a few devices on it.
If you have up to 100 active devices you can create an AWS t2.medium instance. Minimum size of HDD is 8 Gib. At any moment it is possible to add RAM or increase HDD size if necessary.
If you plan to service from 100 to 1000 active assets we recommend to choose m4.xlarge instance type. Size of storage must be over 16 Gib.
For such number of active devices we recommend to choose the m4.4xlarge instance type.
Alternatively, you can use two instances: the first will be used for database and the second for the Java applications (backend) and Web interface (frontend). This option divides previous instance type into two smaller: m4.xlarge for web and java and m4.2xlarge for databases.
There are several ways to deploy Navixy Cloud in this case. The first one is to create instance type r3.4xlarge for all applications(DBMS, java, web). Or distribute the components into three instances. For databases is the best way to use instance type m4.4xlarge. For java applications choose the m4.xlarge. And for web you can create the t2.micro or t2.small. As for static files it is possible to store they on EBS separately.
Change the security group (or create your own). Make ports 80, 8383 and range of 47730-47780 available from the Internet to the server. Don’t forget about 22 port (!) for SSH connection, then launch the instance:
OPTIONAL: Associate elastic IP address to your instance
If you stop or reboot your AWS instance at any time, it’s IP address will change and this will result in web server configuration inconsistency and platform will no longer work until web server is reconfigured. To avoid this problem, AWS have a static IP address called “Elastic IP”.
To associate elastic IP with your instance, open the “Elastic IPs” menu and click the “Associate new address” button
Choose the VPC scope
Your new Elastic IP address will be created. Next, choose “Associate address”, select your Instance and Private IP (which should be the only Private IP available)
After clicking “Associate”, your new Elastic IP address will be associated with your Navixy AWS instance. After this, you can stop and reboot the instance, and it’s functionality will not be affected.