ArcadeDB

In AWS Marketplace, subscribe to the ArcadeDB listing, then click Continue to Launch. Choose your instance type, VPC and subnet, key pair, and a security group that allows TCP 22 from your management IP and TCP 80 from your trusted client networks.

The ArcadeDB HTTP listener is bound to loopback, so only nginx on port 80 is exposed. Do not expose port 80 to the public internet without a TLS-terminating reverse proxy in front.

aws ec2 run-instances \
  --image-id <arcadedb-ami-id> \
  --instance-type m5.large \
  --key-name <your-key> \
  --security-group-ids <your-sg> \
  --subnet-id <your-subnet> \
  --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=arcadedb-01}]'

sudo systemctl is-active arcadedb.service nginx.service
sudo test -f /var/lib/sac/data/arcadedb-firstboot.done && echo FIRSTBOOT_DONE

Both services should report active, and the first-boot sentinel should be present:

active active FIRSTBOOT_DONE

The ArcadeDB HTTP listener is bound to 127.0.0.1:2480, and nginx serves it on port 80. There is no open JMX or management port.

sudo journalctl -u arcadedb.service --no-pager | grep -E 'ArcadeDB Server started|Available query languages' | tail -2 sudo ss -tln | grep -E ':2480|:80 '

You will see ArcadeDB reporting its available query languages and the listeners on loopback 2480 and port 80:

Available query languages: [js, java, sql, sqlscript, opencypher, mongo, graphql, redis, cypher, gremlin] ArcadeDB Server started in 'development' mode (CPUs=2 MAXRAM=1024.00MB) LISTEN 0 511 0.0.0.0:80 0.0.0.0:* LISTEN 0 1000 [::ffff:127.0.0.1]:2480 *:*

The per-instance root password is generated at first boot and stored in a root-only file:

sudo cat /root/arcadedb-credentials.txt

You will see the root user, the per-instance password, and the endpoint URLs:

ARCADEDB_ROOT_USER=root ARCADEDB_ROOT_PASSWORD=<ARCADEDB_PASSWORD> ARCADEDB_STUDIO_URL=http://<instance-public-ip>/ ARCADEDB_HTTP_API_URL=http://<instance-public-ip>/api/v1/ ARCADEDB_DEMO_DATABASE=Demo

ArcadeDB exposes a full REST API. Extract the password into a shell variable, then run an authenticated query against the seeded Demo database:

PW=$(sudo grep '^ARCADEDB_ROOT_PASSWORD=' /root/arcadedb-credentials.txt | cut -d= -f2-)
curl -s -u "root:$PW" http://127.0.0.1/api/v1/databases
curl -s -u "root:$PW" -H 'Content-Type: application/json' -X POST http://127.0.0.1/api/v1/command/Demo \
  -d '{"language":"sql","command":"SELECT name, role FROM Person ORDER BY name"}'

The first call lists the databases (Demo). The second returns the three Person records from the sample graph:

{"version":"26.7.2 ...","user":"root","result":["Demo"]} {"user":"root","result":[{"name":"Alice","role":"Engineer"},{"name":"Bob","role":"Designer"},{"name":"Carol","role":"Analyst"}]}

An unauthenticated request is refused with HTTP 401, and a wrong password is refused with HTTP 403. The API is never open without valid credentials.

ArcadeDB Studio is the built-in web workbench. Open http://<instance-public-ip>/ from your workstation. Your security group must allow TCP 80 from your address. The sign-in page shows the multi-model overview and asks for a username and password:

Sign in with user root and the per-instance password from /root/arcadedb-credentials.txt. Studio connects to the Demo database. It shows the Database Info panel with the seeded schema (Person vertices and Knows edges), plus the query editor:

Type a query into the editor and choose a language. SQL, Open Cypher, Gremlin, GraphQL, MongoDB and Redis are available. Press Run. The Table view shows the returned records:

Switch the result view to Graph to explore vertices and their relationships visually. The Demo graph shows the Person vertices connected by directed Knows edges. A toolbar offers redraw, select, crop, import and export:

ArcadeDB runs several query languages against the same data. Try Cypher against the Demo graph:

PW=$(sudo grep '^ARCADEDB_ROOT_PASSWORD=' /root/arcadedb-credentials.txt | cut -d= -f2-)
curl -s -u "root:$PW" -H 'Content-Type: application/json' -X POST http://127.0.0.1/api/v1/command/Demo \
  -d '{"language":"cypher","command":"MATCH (p:Person)-[:Knows]->(f:Person) RETURN p.name, f.name"}'

The response traverses the Knows relationships:

{"user":"root","result":[{"p.name":"Alice","f.name":"Bob"},{"p.name":"Bob","f.name":"Carol"},{"p.name":"Carol","f.name":"Alice"}]}

You can traverse the same graph with SQL (SELECT expand(out('Knows')) FROM Person) or with Gremlin (g.V().hasLabel('Person').out('Knows').values('name')). ArcadeDB also speaks the MongoDB and Redis wire protocols for document and key-value access.

These are the main components and where they live:

• Server home: /opt/arcadedb
• Start script: /opt/arcadedb/bin/server.sh
• Server environment: /etc/default/arcadedb
• Databases directory: /var/lib/arcadedb/databases (dedicated EBS data volume)
• Server users file: /opt/arcadedb/config/server-users.jsonl
• Systemd unit: /etc/systemd/system/arcadedb.service
• First-boot script: /usr/local/sbin/arcadedb-firstboot.sh
• Credentials file: /root/arcadedb-credentials.txt (mode 0600)
• First-boot sentinel: /var/lib/sac/data/arcadedb-firstboot.done
• nginx site: /etc/nginx/sites-available/sac-arcadedb

sudo systemctl status arcadedb.service --no-pager | head -6 sudo journalctl -u arcadedb.service --no-pager | tail -5

After a configuration change, restart the service with sudo systemctl restart arcadedb.service.

• Rotate the root password in Studio (Security tab) or through the API, and store it in AWS Secrets Manager.
• Keep the HTTP listener on loopback as shipped. Expose only nginx on port 80, and put TLS in front of it (an Application Load Balancer, or nginx with a real certificate).
• Restrict the security group so port 80 reaches only trusted client networks, never the public internet without TLS.
• Create per-application users and roles in the Security tab instead of using the root account for application traffic.
• Back up the databases directory at /var/lib/arcadedb/databases, or snapshot the EBS data volume.
• Patch the OS monthly with sudo apt-get update && sudo apt-get upgrade && sudo reboot.

ArcadeDB is licensed under the Apache License 2.0. There are no per-node, per-CPU or per-GB fees for the software. This image is produced by SecureAnyCloud and is not affiliated with, endorsed by or sponsored by Arcade Data Ltd. ArcadeDB is a trademark of its respective owner and is used here only to describe the software included in the image.

SecureAnyCloud provides commercial support for this image separately from the upstream project.

Email: sales@secureanycloud.com

Website: secureanycloud.com

Support hours: 24/7 with guaranteed 24-hour response SLA

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com

Deploy on AWS

Launch ArcadeDB Multi-Model Database on AWS with 24/7 support from SecureAnyCloud.

View on Marketplace

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com