Specifically, in the Server section, I replaced the domain. Also take note of the http_port as we'll need to create security rule for our Amazon EC2 instance:

#################################### Server ####################################
[server]
# Protocol (http or https)
;protocol = http
# The ip address to bind to, empty will bind to all interfaces
;http_addr =
# The http port to use
;http_port = 3000
# The public facing domain name used to access grafana from a browser
;domain = grafana.catswithwine.com
# The full public facing url
;root_url = %(protocol)s://%(domain)s:%(http_port)s/

Then restart the Grafana service

$ sudo service grafana-server restart

I have my domain registered through Dreamhost, so I went over there next to add the custom DNS record. You'll notice the name is the same domain that I specified in grafana.ini configuration file. The value is the IP address of my Amazon EC2 instance. Note that it can take awhile for these DNS records to propagate around on the internet. It took about 5 minutes before I was able to ping grafana.catswithinwine.com and have it resolve to the IP address.

I then went over to my Amazon EC2 instance and created an inbound security rule so I could access Grafana. Note that you can create Security Groups and then apply them to a specific EC2 instance (or a group of EC2 instances). Just make sure you're adding the rule to the EC2 instance you installed Grafana on (in my case, the EC2 instance with the IP address of 54.191.232.155)

Once you've got that all set up, you should be able to access Grafana:

Since I set up the Amazon EC2 security rule to only allow incoming requests from my IP address, this page is accessible only to me. If I try to access it from a different IP address (say, from a cafe, my phone, or a different ISP) I won't be able to reach this page without adding more security rules.

The default username/password is admin/admin.

Configure Grafana to use InfluxDB as a data source

Before we can make any dashboards we'll need to define the data source.

We'll set up Grafana to use the same HTTP protocol on port 8086 that we used to test reading data from InfluxDB. It's important to tell Grafana to proxy the requests, so each request to InfluxDB comes from Grafana and not from your web browser. Remember that we only opened up port 3000 to Grafana in our EC2 security settings. If you don't proxy the requests, you won't be able to reach InfluxDB without changing some security settings or exposing more ports.

It's interesting to note that you must type a user and password to save this data source, even though the default InfluxDB settings don't care about user/passwords unless you explicitly set them up.

Now go ahead and create your first chart. You should see the two values we inserted earlier.

Next steps

Install StatsD or Telegraf to start sending data to InfluxDB. Alternatively just POST some data to InfluxDB using the HTTP interface on port 8086 whenever you want to.