Deploy Aquarius
About Aquarius
Aquarius is an off-chain component that caches the asset's metadata published on-chain. By deploying their own instance of Aquarius, developers can control which assets are visible in their DApp. For example, having a custom Aquarius instance allows only the assets from specific addresses to be visible in the DApp.
This tutorial will provide the steps to deploy Aquarius. Ocean Protocol provides Aquarius Docker images which can be viewed here. Visit this page to view the Aquarius source code.
Aquarius consists of two parts:
API: The Aquarius API provides a user with a convenient way to access the metadata without scanning the chain itself.
Event monitor: Aquarius continually monitors the chains for MetadataCreated and MetadataUpdated events, processes these events, and adds them to the database.
As mentioned in the Setup a Server document, all Ocean components can be deployed in two configurations: simple, based on Docker Engine and Docker Compose, and complex, based on Kubernetes with Docker Engine. This document will present how to deploy Aquarius in each of these configurations.
Deploying Aquarius using Docker Engine and Docker Compose
This guide will deploy Aquarius, including Elasticsearch as a single systemd service.
Prerequisites
A server for hosting Aquarius. See this guide for how to create a server;
Docker Compose and Docker Engine are installed and configured on the server. See this guide for how to install these products.
The RPC URLs and API keys for each of the networks to which the Aquarius will be connected. See this guide for how to obtain the URL and the API key.
Steps
1. Create the /etc/docker/compose/aquarius/docker-compose.yml file
From a terminal console, create /etc/docker/compose/aquarius/docker-compose.yml file, then copy and paste the following content to it. Check the comments in the file and replace the fields with the specific values of your implementation. The following example is for deploying Aquarius for Goerli network.
For each other network in which you want to deploy Aquarius, add to the file a section similar to "aquarius-events-goerli" included in this example and update the corresponding parameters (i.e. EVENTS_RPC, OCEAN_ADDRESS, SUBGRAPH_URLS) specific to that network.
version: '3.9'
services:
elasticsearch:
image: elasticsearch:8.7.0
container_name: elasticsearch
restart: on-failure
environment:
ES_JAVA_OPTS: "-Xms512m -Xmx512m"
MAX_MAP_COUNT: "64000"
discovery.type: "single-node"
ELASTIC_PASSWORD: "changeme"
xpack.security.enabled: "false"
xpack.security.http.ssl.enabled: "false"
volumes:
- data:/usr/share/elasticsearch/data
ports:
- 9200:9200
networks:
- backend
aquarius:
image: oceanprotocol/aquarius:v5.1.2
container_name: aquarius
restart: on-failure
ports:
- 5000:5000
networks:
- backend
depends_on:
- elasticsearch
environment:
DB_MODULE: elasticsearch
DB_HOSTNAME: http://elasticsearch
DB_PORT: 9200
DB_USERNAME: elastic
DB_PASSWORD: changeme
DB_NAME: aquarius
DB_SCHEME: http
DB_SSL : "false"
LOG_LEVEL: "INFO"
AQUARIUS_URL: "http://0.0.0.0:5000"
AQUARIUS_WORKERS : "4"
RUN_AQUARIUS_SERVER: "1"
AQUARIUS_CONFIG_FILE: "config.ini"
EVENTS_ALLOW: 0
RUN_EVENTS_MONITOR: 0
ALLOWED_PUBLISHERS: '[""]'
aquarius-events-goerli:
image: oceanprotocol/aquarius:v5.1.2
container_name: aquarius-events-goerli
restart: on-failure
networks:
- backend
depends_on:
- elasticsearch
environment:
DB_MODULE: elasticsearch
DB_HOSTNAME: http://elasticsearch
DB_PORT: 9200
DB_USERNAME: elastic
DB_PASSWORD: changeme
DB_NAME: aquarius
DB_SCHEME: http
DB_SSL : "false"
LOG_LEVEL: "INFO"
AQUARIUS_URL: "http://0.0.0.0:5000"
AQUARIUS_WORKERS : "1"
RUN_AQUARIUS_SERVER : "0"
AQUARIUS_CONFIG_FILE: "config.ini"
ALLOWED_PUBLISHERS: '[""]'
NETWORK_NAME: "goerli"
EVENTS_RPC: "https://goerli.infura.io/v3/<infura_id>"
METADATA_UPDATE_ALL : "0"
OCEAN_ADDRESS : 0xcfdda22c9837ae76e0faa845354f33c62e03653a
RUN_EVENTS_MONITOR: 1
BLOCKS_CHUNK_SIZE: "5000"
SUBGRAPH_URLS: "5: https://v4.subgraph.goerli.oceanprotocol.com"
volumes:
data:
driver: local
networks:
backend:
driver: bridge2. Create the /etc/systemd/system/[email protected] file
Create the /etc/systemd/system/[email protected] file then copy and paste the following content to it. This example file could be customized if needed.
[Unit]
Description=%i service with docker compose
Requires=docker.service
After=docker.service
[Service]
Type=oneshot
RemainAfterExit=true
Environment="PROJECT=ocean"
WorkingDirectory=/etc/docker/compose/%i
ExecStartPre=/usr/bin/env docker-compose -p $PROJECT pull
ExecStart=/usr/bin/env docker-compose -p $PROJECT up -d
ExecStop=/usr/bin/env docker-compose -p $PROJECT stop
ExecStopPost=/usr/bin/env docker-compose -p $PROJECT down
[Install]
WantedBy=multi-user.target3. Reload the systemd manager configuration
Run the following command to reload the systemd manager configuration
sudo systemctl daemon-reloadOptionally, you can enable the services to start at boot, using the following command:
sudo systemctl enable [email protected]4. Start Aquarius service
To start the Aquarius service, run the following command:
sudo systemctl start [email protected]5. Check the service's status
Check the status of the service by running the following commands:
sudo systemctl status [email protected]6. Confirm Aquarius is accessible
Run the following commands to access Aquarius The output should be similar to the one displayed here.
$ curl localhost:9200
{
"name" : "a93d989293ac",
"cluster_name" : "docker-cluster",
"cluster_uuid" : "Bs16cyCwRCOIbmaBUEj5fA",
"version" : {
"number" : "8.7.0",
"build_flavor" : "default",
"build_type" : "docker",
"build_hash" : "09520b59b6bc1057340b55750186466ea715e30e",
"build_date" : "2023-03-27T16:31:09.816451435Z",
"build_snapshot" : false,
"lucene_version" : "9.5.0",
"minimum_wire_compatibility_version" : "7.17.0",
"minimum_index_compatibility_version" : "7.0.0"
},
"tagline" : "You Know, for Search"
}$ curl localhost:5000
{"plugin":"module","software":"Aquarius","version":"5.1.2"}7. Use Docker CLI to check the Aquarius service's logs
If needed, use docker CLI to check Aquarius' service logs.
First, identify the container id:
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
355baee34d50 oceanprotocol/aquarius:v5.1.2 "/aquarius/docker-en…" About a minute ago Up About a minute 5000/tcp aquarius-events-goerli
f1f97d6f146f oceanprotocol/aquarius:v5.1.2 "/aquarius/docker-en…" About a minute ago Up About a minute 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp aquarius
a93d989293ac elasticsearch:8.7.0 "/bin/tini -- /usr/l…" About a minute ago Up About a minute 0.0.0.0:9200->9200/tcp, :::9200->9200/tcp, 9300/tcp elasticsearch
Then, check the logs from the Aqauarius' Docker containers:
$ docker logs aquarius [--follow]
$ docker logs aquarius-events-goerli [--follow]Deploying Aquarius using Kubernetes
Aquarius depends on the backend database and in this example we will deploy the following resources:
Elasticsearch.
Aquarius (Deployment)
Templates (yaml files) are provided and could be customized based on the environment's specifics.
Prerequisites
A server for hosting Aquarius. See this guide for how to create a server;
Kubernetes with Docker Engine is installed and configured on the server. See this chapter for information on installing Kubernetes.
The RPC URLs and API keys for each of the networks to which the Aquarius will be connected. See this guide for how to obtain the URL and the API key.
Steps
1. Deploy Elasticsearch
It is recommended to deploy Elasticsearch through Helm chart.
a. Once the Elasticsearch pods are running, the database service should be available:
$ kubectl port-forward --namespace ocean svc/elasticsearch-master 9200:9200
Forwarding from 127.0.0.1:9200 -> 9200
Forwarding from [::1]:9200 -> 9200b. Check that the Elasticsearch service is accessible:
$ curl localhost:9200
{
"name" : "elasticsearch-master-2",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "KMAfL5tVSJWFfmCOklT0qg",
"version" : {
"number" : "8.5.2",
"build_flavor" : "default",
"build_type" : "docker",
"build_hash" : "a846182fa16b4ebfcc89aa3c11a11fd5adf3de04",
"build_date" : "2022-11-17T18:56:17.538630285Z",
"build_snapshot" : false,
"lucene_version" : "9.4.1",
"minimum_wire_compatibility_version" : "7.17.0",
"minimum_index_compatibility_version" : "7.0.0"
},
"tagline" : "You Know, for Search"
}2. Deploy Aquarius
Aquarius supports indexing multiple chains using a single instance to serve API requests and one instance for each chain that must be indexed.
The following deployment templates could be used for guidance. Some parameters are optional and the template could be adjusted based on these considerations. Common cases are the deployments for one/multiple Ethereum networks:
Mainnet
Sepolia
a. Create a YAML file for Aquarius configuration.
The following templates (annotated) could be edited and used for deployment.
aquarius-deployment.yaml (annotated): this deployment is responsible for serving API requests
apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
labels:
app: aquarius
name: aquarius
spec:
progressDeadlineSeconds: 600
replicas: 1
revisionHistoryLimit: 5
selector:
matchLabels:
app: aquarius
strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate
template:
metadata:
creationTimestamp: null
labels:
app: aquarius
spec:
containers:
- env:
- name: LOG_LEVEL
value: DEBUG
- name: AQUARIUS_URL
value: http://0.0.0.0:5000
- name: AQUARIUS_WORKERS
value: "4"
- name: DB_HOSTNAME
value: < ES service hostname >
- name: DB_MODULE
value: elasticsearch
- name: DB_NAME
value: aquarius
- name: DB_PORT
value: "9200"
- name: DB_SCHEME
value: http
- name: DB_USERNAME
value: < ES username >
- name: DB_PASSWORD
value: < ES password >
- name: DB_SSL
value: "false"
- name: RUN_AQUARIUS_SERVER
value: "1"
- name: RUN_EVENTS_MONITOR
value: "0"
- name: EVENTS_ALLOW
value: "0"
- name: CONFIG_FILE
value: config.ini
- name: ALLOWED_PUBLISHERS
value: '[""]'
image: oceanprotocol/aquarius:v5.1.2 => check the available versions: https://hub.docker.com/repository/docker/oceanprotocol/aquarius/tags?page=1&ordering=last_updated
imagePullPolicy: Always
livenessProbe:
failureThreshold: 3
httpGet:
path: /
port: 5000
scheme: HTTP
initialDelaySeconds: 20
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 2
name: aquarius
ports:
- containerPort: 5000
protocol: TCP
readinessProbe:
failureThreshold: 3
httpGet:
path: /
port: 5000
scheme: HTTP
initialDelaySeconds: 20
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
resources:
limits:
cpu: 800m
memory: 1Gi
requests:
cpu: 800m
memory: 1Gi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
terminationGracePeriodSeconds: 30yaExample deployment for Sepoia (Polygon testnet):
aquarius-events-sepolia-deployment.yaml (annotated) - this deployment will be responsible for indexing the block and storing the metadata published on-chain:
apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
labels:
app: aquarius-events-sepolia
name: aquarius-events-sepolia
spec:
progressDeadlineSeconds: 600
replicas: 1
revisionHistoryLimit: 5
selector:
matchLabels:
app: aquarius-events-sepolia
strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate
template:
metadata:
creationTimestamp: null
labels:
app: aquarius-events-sepolia
spec:
containers:
- env:
- name: LOG_LEVEL
value: DEBUG
- name: AQUARIUS_URL
value: http://0.0.0.0:5000
- name: AQUARIUS_WORKERS
value: "1"
- name: DB_HOSTNAME
value: < ES service hostname >
- name: DB_MODULE
value: elasticsearch
- name: DB_NAME
value: aquarius
- name: DB_PORT
value: "9200"
- name: DB_SCHEME
value: http
- name: DB_USERNAME
value: < ES username >
- name: DB_PASSWORD
value: < ES password >
- name: DB_SSL
value: "false"
- name: RUN_AQUARIUS_SERVER
value: "0"
- name: RUN_EVENTS_MONITOR
value: "1"
- name: CONFIG_FILE
value: config.ini
- name: ALLOWED_PUBLISHERS
value: '[""]'
- name: NETWORK_NAME
value: sepolia
- name: EVENTS_RPC
value: https://polygon-sepolia.infura.io/v3/< INFURA ID > => or another RPC service for this network
- name: METADATA_UPDATE_ALL
value: "0"
- name: ASSET_PURGATORY_URL
value: https://raw.githubusercontent.com/oceanprotocol/list-purgatory/main/list-assets.json
- name: ACCOUNT_PURGATORY_URL
value: https://raw.githubusercontent.com/oceanprotocol/list-purgatory/main/list-accounts.json
- name: PURGATORY_UPDATE_INTERVAL
value: "60"
- name: OCEAN_ADDRESS
value: 0xd8992Ed72C445c35Cb4A2be468568Ed1079357c8
- name: SUBGRAPH_URLS
value: |
{"80001": "https://v4.subgraph.sepolia.oceanprotocol.com"} => or your own deployed Ocean Subgraph service for this network
- name: BLOCKS_CHUNK_SIZE
value: "3500"
- name: EVENTS_HTTP
value: "1"
image: oceanprotocol/aquarius:v5.1.2 => check the available versions: https://hub.docker.com/repository/docker/oceanprotocol/aquarius/tags?page=1&ordering=last_updated
imagePullPolicy: Always
livenessProbe:
failureThreshold: 3
httpGet:
path: /
port: 5001
scheme: HTTP
initialDelaySeconds: 20
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
name: aquarius-events-sepolia
ports:
- containerPort: 5000
protocol: TCP
readinessProbe:
failureThreshold: 3
httpGet:
path: /
port: 5001
scheme: HTTP
initialDelaySeconds: 20
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
resources:
limits:
cpu: 500m
memory: 1Gi
requests:
cpu: 500m
memory: 1Gi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
terminationGracePeriodSeconds: 30Tip: before deployment, you can validate the yaml file.
b. Deploy the configuration
Deploy the configuration in Kubernetes using the following commands.
$ kubectl apply -f aquarius-deployment.yaml
$ kubectl apply -f aquarius-events-rinkeby-deployment.yaml
kubectl get pods -l app=aquarius
NAME READY STATUS RESTARTS AGE
aquarius-6fd9cc975b-fxr4d 1/1 Running 0 1d
kubectl get pods -l app=aquarius-events-sepolia
NAME READY STATUS RESTARTS AGE
aquarius-events-sepolia-8748976c4-mh24n 1/1 Running 0 1dCheck the logs for newly deployed Aquarius by running the following command:
$ kubectl logs aquarius-6fd9cc975b-fxr4d [--follow]
$ kubectl logs aquarius-events-sepolia-8748976c4-mh24n [--follow]c. Create a Kubernetes service
The next step is to create a Kubernetes service (eg. ClusterIP, NodePort, Loadbalancer, ExternalName) for this deployment, depending on the environment specifications. Follow this link for details on how to create a Kubernetes service.
Last updated
Was this helpful?