After creating the Admin user (in case of Redash AMI) or logging in using the credentials found in the system log (in case of Bitnami AMI), we should see the following screen, where the user will be guided through a short quickstart setup:

Before we can declare the installation as complete, let's SSH to the machine and check what processes are running there. In our example, the user is bitnami.

First, we SSH into the machine using the following code:

ssh -i $PATH_TO_YOUR_PEM_KEY bitnami@$PUBLIC_IP_OF_THE_MACHINE

When inside the machine, run the following code: 

ps -ef | grep redash

We should get something similar to the following output:

redash_gunicorn - redash web app (we can see the parent process with pid 1912, and 4 child processes: 2052, 2053, 2054, 2055):

redash 1912 1 0 May13 ? 00:02:07 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/gunicorn -b 127.0.0.1:5000 --pid /opt/bitnami/apps/redash/logs/redash_gunicorn.pid --log-file /opt/bitnami/apps/redash/logs/redash_gunicorn.log --name redash -w 4 --max-requests 1000 redash.wsgi:app

redash 2052 1912 0 May13 ? 00:00:18 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/gunicorn -b 127.0.0.1:5000 --pid /opt/bitnami/apps/redash/logs/redash_gunicorn.pid --log-efile /opt/bitnami/apps/redash/logs/redash_gunicorn.log --name redash -w 4 --max-requests 1000 redash.wsgi:app
 
 redash 2053 1912 0 May13 ? 00:00:19 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/gunicorn -b 127.0.0.1:5000 --pid /opt/bitnami/apps/redash/logs/redash_gunicorn.pid --log-file /opt/bitnami/apps/redash/logs/redash_gunicorn.log --name redash -w 4 --max-requests 1000 redash.wsgi:app

redash 2054 1912 0 May13 ? 00:00:19 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/gunicorn -b 127.0.0.1:5000 --pid /opt/bitnami/apps/redash/logs/redash_gunicorn.pid --log-file /opt/bitnami/apps/redash/logs/redash_gunicorn.log --name redash -w 4 --max-requests 1000 redash.wsgi:app

redash 2055 1912 0 May13 ? 00:00:20 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/gunicorn -b 127.0.0.1:5000 --pid /opt/bitnami/apps/redash/logs/redash_gunicorn.pid --log-file /opt/bitnami/apps/redash/logs/redash_gunicorn.log --name redash -w 4 --max-requests 1000 redash.wsgi:app

The job of Celery worker processes (which has a parent with a pid of 1934 and 3 child processes) is to run the ad-hoc queries as well as other tasks (for example, sending an email):

 redash 1934 1 0 May13 ? 00:37:54 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/celery worker --pidfile /opt/bitnami/apps/redash/logs/redash_celery_worker.pid --app=redash.worker --beat -c2 -Qqueries,celery --maxtasksperchild=10 -Ofair
redash 2058 1934 0 May13 ? 00:01:27 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/celery worker --pidfile /opt/bitnami/apps/redash/logs/redash_celery_worker.pid --app=redash.worker --beat -c2 -Qqueries,celery --maxtasksperchild=10 -Ofair
 redash 28495 1934 0 09:02 ? 00:00:01 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/celery worker --pidfile /opt/bitnami/apps/redash/logs/redash_celery_worker.pid --app=redash.worker --beat -c2 -Qqueries,celery --maxtasksperchild=10 -Ofair
 redash 28502 1934 0 09:04 ? 00:00:01 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/celery worker --pidfile /opt/bitnami/apps/redash/logs/redash_celery_worker.pid --app=redash.worker --beat -c2 -Qqueries,celery --maxtasksperchild=10 -Ofair

Celery's scheduled queries queue worker processes (which has a parent with a pid of 1955 and 2 children), and their task is to process the scheduled queries:

 redash 1955 1 0 May13 ? 00:18:51 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/celery worker --pidfile /opt/bitnami/apps/redash/logs/redash_celery_scheduled.pid --app=redash.worker -c2 -Qscheduled_queries --maxtasksperchild=10 -Ofair
 
redash 2047 1955 0 May13 ? 00:00:01 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/celery worker --pidfile /opt/bitnami/apps/redash/logs/redash_celery_scheduled.pid --app=redash.worker -c2 -Qscheduled_queries --maxtasksperchild=10 -Ofair

 redash 2061 1955 0 May13 ? 00:00:01 /opt/bitnami/apps/redash/htdocs/venv/bin/python /opt/bitnami/apps/redash/htdocs/venv/bin/celery worker --pidfile /opt/bitnami/apps/redash/logs/redash_celery_scheduled.pid --app=redash.worker -c2 -Qscheduled_queries --maxtasksperchild=10 -Ofair

PostgreSQL database processes:

 postgres 2138 842 0 May13 ? 00:00:00 postgres: bn_redash bitnami_redash 127.0.0.1(58991) idle
 postgres 2142 842 0 May13 ? 00:00:00 postgres: bn_redash bitnami_redash 127.0.0.1(59000) idle
 postgres 2161 842 0 May13 ? 00:00:00 postgres: bn_redash bitnami_redash 127.0.0.1(59007) idle
 postgres 2440 842 0 May13 ? 00:00:00 postgres: bn_redash bitnami_redash 127.0.0.1(59070) idle
 postgres 28499 842 0 09:03 ? 00:00:00 postgres: bn_redash bitnami_redash 127.0.0.1(43470) idle
 postgres 28507 842 0 09:05 ? 00:00:00 postgres: bn_redash bitnami_redash 127.0.0.1(43473) idle

From the preceding code, we can see the following:

• Postgres DB process (and its workers)
• Redis
• Celery workers
• Gunicorn: The WSGI HTTP Server (that actually serves the Redash app)

Now, we can consider the installation as complete.