-
Make sure to run
aws configureand set the correct keys and region -
Add your RDFox.lic file to the directory
-
Run the following commands to configure the license, role name, and role password. Replace the values
adminandpasswordbelow:aws ssm put-parameter --name "/rdfox/role" --value admin --type "String" --overwrite aws ssm put-parameter --name "/rdfox/role-password" --value password --type "String" --overwrite aws ssm put-parameter --name "/rdfox/license" --type "String" --value "$(cat RDFox.lic)" --overwrite -
From the AWS Management Console, open CloudFormation and deploy the template.yaml file. During the deployment, you'll need to specify:
- Your VPC
- Two subnets inside your VPC. For resiliency, the fargate service is allowed to launch in any of the 3 subnets specified.
- CPU and memory settings for the Fargate instance. Please keep in mind that RDFOX is an in-memory database and Fargate's CPU and memory options defined here: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/AWS_Fargate.html
- The FQDN for RDFOX, for example:
rdfox.mydomain.com - The Listener ARN for your Application Load Balancer
- The Listener Priority for your Application Load Balancer
-
Add a DNS for the FQDN pointing at the Application Load Balancer. You can access RDFOX only using the FQDN.
-
After the Fargate service is up and running, you can access RDFOX at:
https://<FQDN>/console
rbilleci/aws-neptune-rdfox
Folders and files
| Name | Name | Last commit date | ||
|---|---|---|---|---|