The self-managed version of GraphDB is a hosted database in the Cloud providing all the power of a scalable triple store as a pay-by-the-hour service through Amazon Web Services. GraphDB (Standard Edition) can be purchased as an AMI running on EC2 instances with 4-core / 32 GB RAM or or 8-core / 64 GB RAM.
Our customers often tell us that they want to develop and test in the cloud before bringing projects in-house. Now, you can do that without the need for buying GraphDB licenses or provision hardware first - GraphDB in the Cloud is perfect for running limited-time projects or low-volume experiments in a production-quality setting without an investment in hardware.
All GraphDB instances are designed to store data on user-supplied Amazon EBS volumes (network attached storage), so that your data is persisted and safe even if the instance is not running. GraphDB in the Cloud is accessible via standard RESTful APIs and SPARQL endpoints
The following Amazon Web Services concepts which are related to running GraphDB on the AWS cloud:
GraphDB in the AWS cloud is available in various server configurations:
The EC2 cost depends on the type of instance being used - on demand instances are optimal only for short term and occasional use, while reserved instances are optimal for longer term and more frequent use.
In order to use GraphDB on AWS you need the following:
The process of configuring and starting GraphDB in the AWS cloud involves the following steps:
The following diagram shows the sequence of steps to be followed:
After an EC2 instance with GraphDB is activated and the GraphDB server is started the customer may access it via the public IP address of the particular EC2 instance as:
The script verifies that the EBS data volume is properly attached and creates a mount point for it. If the EBS volume is not attached yet for some reason, the script prompts the user for that and performs several delayed retries giving time to the user to attach the volume via the AWS Management Console. If the time is not sufficient this script should be rerun again.
On successful execution of the script confirms that the volume is mounted and prints out the mount point location: /data_mount/data.
The script will verify that the data volume is available (if not it terminates with a reminder message) and will start the service:
If the data volume attached was used previously, the old repositories will be detected and listed under Admin > repositories.
It will perform various automated tests like creating a repository, loading some data, query the data and delete the repository. Results from each test is printed in the console.
The termination of the GraphDB service should be done only via the provided shell script:
This will perform a graceful shutdown of the service persisting any in memory data to the EBS volume. This operation might take some time so be sure there's no active java process prior to restarting the service or terminating the EC2 instance.
The GraphDB service can be started again at any time (only possible if the EC2 is stopped rather than terminated) with these steps:
The EC2 resources can be completely or partially released depending on the use case requirements:
By default, the user management and security is disabled. To enable it, go to Administration > Users and enable the Security option
The default login for the 'admin' user is with password 'root'. Make sure you change the password as soon as the security is enabled!
Detailed description is available at: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html
Backing up the data is a simple process of taking snapshot of the EBS data volume. The snapshot then can be used for restoring the application data state or for replication of the data or migrating it to other data center.
The proper order of steps for data backup are:
Data restore steps (on running AWS instance):
Data restore steps (new AWS instance):
The standard support channels are available for questions, feedback and general information related to GraphDB on AWS:
Skip to end of metadata Go to start of metadata