[~aloraine]

The Command That should be run from the SSH is:
:ssh user@PublicIPAddress -L 5601:localhost:5601
1) Replace user with the login username.
2) PublicIpAdress is the IPAdress of the machine where the ELK Stack is installed. In this case IP Address of
the EC2 Instance.
3) 5601:localhost:5601 signifies redirecting the localhost:5601 connections to the port 5601 of the machine
which was given as PublicIPAddress.
WINDOWS INSTRUCTIONS USING PUTTY
-----------------------------------------------------------------------------
For windows, please go through the instructions to setup ssh tunnel.
https://www.skyverge.com/blog/how-to-set-up-an-ssh-tunnel-with-putty/

I have updated the reference document. I have installed the ELK stack on my virtual ubuntu machine, because to allow kibana and elastic search to allow remote connections on ec2 instance, we might need to increase the heap size as our current configuration of 250mb is raising a concern.

https://stackoverflow.com/questions/41260571/elasticsearch-wont-start-when-binding-to-anything-but-localhost-node-validatio
https://www.elastic.co/guide/en/elasticsearch/reference/current/setting-system-settings.html

Follow-up questions:

• To view the Dashboard, I should set up an ssh tunnel and then open localhost:5601 in my Web browser?

Is that right?

• Please do a bit of research into the ssh command line call to set up the ssh tunnel.

For example, is it:

• ssh -L 80:[your EC2 public IP]:5601 ubuntu@[your EC2 public IP]

According to https://www.howtogeek.com/168145/how-to-use-ssh-tunneling/, the syntax is:

• ssh -L local_port:remote_address:remote_port username@server.com

However, I don't know what the local and remote ports should be.

To test, do you want to send me the IP address of your VM and I can try it on my Mac laptop, since I have ssh command line already installed and configured?

Find the Attachment for Setup Instructions of ELK Stack on Ubuntu based EC2 Machine.
As per the discussion, Not implementing ELK due to its need for new VM's, development cost , heavy weight requirements.
Will Consider Native Django Based logging options and Django Admin Panel to View the logs.

Found one more useful link related to Django logging:
https://eu.scalyr.com/blog/getting-started-quickly-with-django-logging

Django Based Logging :
https://lincolnloop.com/blog/django-logging-right-way/