This document details the procedure for creating an eagle-i institutional node as a virtual server (or instance) in the Amazon Elastic Compute Cloud (or EC2). Once created, the eagle-i node will operate entirely in the cloud. However, you will retain administrative responsibility over its operation and maintenance, and in particular, you will be responsible for running upgrade scripts when new eagle-i software is released. We do not expect these tasks to be complex, though basic Unix skills are desirable. This solution is ideal for institutions that want to evaluate eagle-i or participate in the eagle-i network but do not have easy access to a data center service. Naturally, the AWS service will incur operational costs (for pricing details, consult the AWS website).
The installation procedure is simple and does not require specialized technical skills. It will allow you to get an eagle-i node up and running in a short amount of time. For a production system, you may need to involve your IT department, in a limited way.
1. Getting ready
2. Installation Procedures
3. Customize eagle-i node
For an evaluation node, there is no need to customize the installation any further. Using the public DNS as your hostname, you may now go to a browser and navigate to the eagle-i node to begin entering data, searching data, accessing the repository, etc. See verify the eagle-i node is up and running for more information on where to navigate to.
- Prepare to Customize eagle-i Node
- Customize eagle-i Repository
- Create system users
- Customize public SPARQL endpoint
- Update node configuration file
4. Verify installation
5. Production instance only
There are additional steps that need to happen in order to make your instance production ready. For more information about elastic IP address, please see the Amazon Documentation: Elastic IP Addresses.
Getting a time out error when trying to navigate to the application in a browser
Double check your security groups and make sure that inbound traffic on HTTPS is allowed.
Error when running finish-install.sh : FAILED to create metadata for user, HTTP status=302
The repository url must match exactly. Typically this happens when http is typed instead of https.