Install Netdata on AWS
Netdata is fully compatible with Amazon Web Services (AWS). You can install Netdata on cloud instances to monitor the apps/services running there, or use multiple instances in a parent-child streaming configuration.
Recommended installation method
The best installation method depends on the instance's operating system, distribution, and version. For Linux instances,
we recommend the
kickstart.sh automatic installation script.
If you have issues with Netdata after installation, look to the sections below to find the issue you're experiencing, followed by the solution for your provider.
Add a firewall rule to access Netdata's dashboard
If you cannot access Netdata's dashboard on your cloud instance via
http://HOST:19999, and instead get an error page
from your browser that says, "This site can't be reached" (Chrome) or "Unable to connect" (Firefox), you may need to
configure your cloud provider's firewall.
Cloud providers often create network-level firewalls that run separately from the instance itself. Both AWS and Google Cloud Platform calls them Virtual Private Cloud (VPC) networks. These firewalls can apply even if you've disabled firewalls on the instance itself. Because you can modify these firewalls only via the cloud provider's web interface, it's easy to overlook them when trying to configure and access Netdata's dashboard.
You can often confirm a firewall issue by querying the dashboard while connected to the instance via SSH:
http://localhost:19999/api/v1/info. If you see JSON output, Netdata is running properly. If you try the same
command from a remote system, and it fails, it's likely that a firewall is blocking your requests.
Another option is to put Netdata behind web server, which will proxy requests through standard HTTP/HTTPS ports (80/443), which are likely already open on your instance. We have a number of guides available:
Sign in to the AWS console and navigate to the EC2 dashboard. Click on the Security Groups link in the navigation, beneath the Network & Security heading. Find the Security Group your instance belongs to, and either right-click on it or click the Actions button above to see a dropdown menu with Edit inbound rules.
Add a new rule with the following options:
Type: Custom TCP
Port Range: 19999
You can also choose My IP as the source if you prefer.
Click Save to apply your new inbound firewall rule.
Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.