Acceldata
Pulse

Last updated: Sep 26, 2026 20:31 UTC

Configure the Cluster for a Fresh Pulse Installation

These steps are applicable only for a fresh installation. If a cluster is already configured in your Pulse Kubernetes environment, you can safely skip these steps.


Initialize the Manager Server

Send a request to the /init API of the Manager Server with the Pulse image tag and required configuration details.

Steps:

  • Update all placeholder values enclosed in angle brackets (<>).
  • Run the following command:
curl --request POST \
  --url http://<Ingress API for Manager Server>/api/v1/mserver/init \
  --header 'Authorization: <Basic Credentials> \
  --header 'Content-Type: application/json' \
  --data '{
    "pulse_version": "<Pulse Version>",
    "registry_url": "191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata",
    "hdfs_retention_days": 31,
    "mongo_retention_days": 32,
    "logstore_retention": 32,
    "metrics_retention": 32,
    "registry_secret": "<registry secret name>"
  }'


Upload Elasticsearch CA Certificates (VM/Bare-Metal Deployments Only)

If the databases are installed on virtual machines (VMs) or bare-metal machines, upload the CA certificates for the Elasticsearch deployment.

Run the following command:

curl --request PUT \
  --url http://<Ingress API for Manager Server>/api/v1/mserver/upload/certs/es \
  --header 'Authorization: <Basic Credentials> \
  --header 'Content-Type: multipart/form-data' \
  --form es-certs.p12=@cacerts


Deploy Databases (VM/Bare-Metal Deployments Only)

If the databases are installed on virtual machines (VMs) or bare-metal machines, invoke the database deployment API.

Run the following command:

curl --request PUT \
  --url http://<Ingress API for Manager Server>/api/v1/mserver/deploy/db \
  --header 'Authorization: <Basic Credentials> \


Verify Database Containers (VM/Bare-Metal Deployments Only)

After the deployment completes, verify that all database services are running.

On one of the database nodes, run the following command:

docker ps

Example output:

CONTAINER ID   IMAGE                                                                              COMMAND                  CREATED          STATUS          PORTS                                                                       NAMES
4ec76f69e923   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-database:4.1.2-030626    "/run.sh"                48 minutes ago   Up 48 minutes   0.0.0.0:27017->27017/tcp                                                    ad-db-router_default
ef9d93348e6e   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-vminsert:4.1.2-030626    "/run.sh"                48 minutes ago   Up 48 minutes   8480/tcp, 8489/tcp, 0.0.0.0:19043->8427/tcp                                 ad-vminsert_default
ae15334cb2af   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-vmselect:4.1.2-030626    "/run.sh"                48 minutes ago   Up 48 minutes   0.0.0.0:19042->8481/tcp                                                     ad-vmselect_default
7a6b82f0852f   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-vmstorage:4.1.2-030626   "/run.sh"                48 minutes ago   Up 48 minutes   8482/tcp, 0.0.0.0:19122->8400/tcp, 0.0.0.0:19123->8401/tcp                  ad-vmstorage_default
249351f860a4   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-redis:4.1.2-030626       "docker-entrypoint.s…"   48 minutes ago   Up 48 minutes   0.0.0.0:6379->6379/tcp                                                      ad-redis_default
2c5950ed8372   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-pg-ui:4.1.2-030626       "docker-entrypoint.s…"   48 minutes ago   Up 48 minutes   0.0.0.0:19068->5432/tcp                                                     ad-pg-ui_default
e2cb4b307d8a   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-gauntlet:4.1.2-030626    "/bin/sh -c /gauntle…"   48 minutes ago   Up 48 minutes                                                                               ad-gauntlet_default
c2ea9684c188   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-events:4.1.2-030626      "nats-server --confi…"   48 minutes ago   Up 48 minutes   0.0.0.0:19009->4222/tcp, 0.0.0.0:19008->6222/tcp, 0.0.0.0:19007->8222/tcp   ad-events_default
4108c0bf1781   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-database:4.1.2-030626    "/run.sh"                48 minutes ago   Up 48 minutes   0.0.0.0:27019->27017/tcp                                                    ad-db-sh1rs1_default
a8416a9c740a   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-database:4.1.2-030626    "/run.sh"                48 minutes ago   Up 48 minutes   0.0.0.0:27018->27017/tcp                                                    ad-db-config_default
f24560a1f929   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-logstash:4.1.2-030626    "/usr/local/bin/dock…"   48 minutes ago   Up 48 minutes   0.0.0.0:19012->5044/tcp, 0.0.0.0:19051->19015/tcp                           ad-logstash_default
869f96d5a848   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-elastic:4.1.2-030626     "/bin/tini -- /usr/l…"   48 minutes ago   Up 48 minutes   0.0.0.0:19013->9200/tcp, 0.0.0.0:19014->9300/tcp                            ad-elastic_default
e3cc0d3f0f88   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-database:4.1.2-030626    "/run.sh"                48 minutes ago   Up 48 minutes   0.0.0.0:27021->27017/tcp                                                    ad-db-sh3rs1_default
d5ed446fcfe5   191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata/ad-database:4.1.2-030626    "/run.sh"                48 minutes ago   Up 48 minutes   0.0.0.0:27020->27017/tcp                                                    ad-db-sh2rs1_default

Info

The number of containers deployed on a database VM or bare-metal machine depends on the total number of nodes configured for the Pulse Kubernetes deployment.

MongoDB data is both replicated and sharded. For example, if three nodes are configured:

  • Three shards are created.
  • Each shard contains three replicas.

This results in a total of nine MongoDB data-bearing instances across the cluster.


Verify Database Status

After the deployment completes, verify the database status.

Run the following command:

curl --request GET \
  --url http://<Ingress API for Manager Server>/api/v1/mserver/dbstatus \
  --header 'Authorization: <Basic Credentials> \