Launching a Private EC2 Instance of the C-Phrase AMI
You may subscribe to the C-Phrase AMI and launch it as an EC2 instance on AWS. In this case, you have complete control over your data and do not need to take contact with us to use C-Phrase.
This video shows a launch of such an EC2 instance. You may pick between several different types of instances:
- t3.micro (if available) will give you reasonable performance for a single user or small team over moderately sized databases. It will give you burstable support under activity spikes. As you deploy NLIs over larger databases or if you need to run many simultaneous interfaces, you may experience memory limitations. If this is the case, you can increase the instance size to small , medium , large or 2xlarge depending on your needs.
- t2.micro is similar to the t3 instance type, but it will limit burstable support if usage spikes over longer durations.
- r5dn.large is for NLIs over very large databases, where many users are performing either very large data uploads or are asking many complex questions.
Finally, remember for the best interactive performance, you should launch C-Phrase in a region close to where your users are running their browsers.
User-data on Launch
As shown in this video, it is recommended that during EC2 launch you provide the following advanced detail user-data as text:
This will run the Admin Server at launch so you will not need to SSH into the EC2 instance to start it
manually. Assuming that you did not alter the default security group, after launch,
just point your browser at port 9999 of the public IP address of the EC2 instance (e.g.
Note initially you must access this using
https. Once you connect,
you will be presented with a log in screen. The initial username is "admin" and the password is the id of your
EC2 instance. Loging in will bring you to the Admin Interface.
Note that your access to C-Phrase is insecure at this time. The packets exchanged between browsers and the C-Phrase EC2 instance are unencrypted. To secure C-Phrase, you will need to configure HTTPS.
Alternatively you may afford yourself some degree of security by manually restricting the IPs that can access various ports within your default security policy.