How is Grafana accessible when setup via docker on aws ec2

Grafana
1

Hi,
I am using a repo where a docker container for Grafana is being spinned up on the fly. I wanted to know how can I access the Grafana UI?

Config of my ec2 instance:
Ubuntu: 16.04

What I have tried till now:
Tried accessing via the ipaddress of ec2 instance, tried all ip’s with port 3000 listed on ifconfig of ec2 instance.

Able to see this msg in the Grafana log but its not accessible from here too:
msg=“HTTP Server Listen” logger=http.server address=0.0.0.0:3000 protocol=http subUrl= socket=

Do I need to make any edits to my was security group? mine is default with inbound and outbound rules as below:
inbound:
SSH
TCP
22
0.0.0.0/0

Outbound:
All traffic
All
All
0.0.0.0/0

Any ideas will be appreciated. Thanks!!

2

Hi,
I am using a repo where a docker container for Grafana is being spinned up
on the fly.

When you say “on the fly”, what do you mean? What causes this instance to be
created?

Also, where is its data source?

I wanted to know how can I access the Grafana UI?

Config of my ec2 instance:
Ubuntu: 16.04

What I have tried till now:
Tried accessing via the ipaddress of ec2 instance,

Accessing from where?

Outside EC2, or inside your own network there?

tried all ip’s with port 3000 listed on ifconfig of ec2 instance.

Able to see this msg in the Grafana log but its not accessible from here

Where is “here”?

too: msg=“HTTP Server Listen” logger=http.server address=0.0.0.0:3000
protocol=http subUrl= socket=

Do I need to make any edits to my was security group? mine is default with
inbound and outbound rules as below: inbound:
SSH
TCP
22
0.0.0.0/0

Well, surely you need to add a rule for inbound access to port 3000?

Antony.

3

Hi,
Thanks for your reply. Please find my answers below:

The instance is created using docker-compose where it spins up a container for JMeter, Grafana and InfluxDB which is the data source.
Accessing from the network outside ec2-----is there a way to access via ec2 network?

IN this case here is referring to 0.0.0.0:3000 (this is the log entry when the docker container for Grafana is spun up- after this it creates influx db container)
too: msg=“HTTP Server Listen” logger=http.server address=0.0.0.0:3000
protocol=http subUrl= socket=

I will add the inbound access to port 3000 and try again. Thanks!!

4

Hi ,
Adding the inbound role for port 3000 fixed the issue. Its accessible via the public ip. Thanks!!