I blocked outgoing TCP connections from the web interface (Networking -> Firewall). Only allowed external 3rd party API ip addresses and DNS.
The problem is that do-agent stopped reporting performance metrics. If I allow all IPv4 outgoing connections everything works fine. But I would like to only premit certain IP addresses for security reasons.
Do you know which IP address do I need to whitelist for do-agent to resume working?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Accepted Answer
The DigitalOcean Monitoring agent requires outbound TCP access on ports 80 and 443 to authenticate to the Monitoring service and to send metrics.
The agent need to be able to access the DigitalOcean metadata API at: http://169.254.169.254/metadata/v1/ as well as the metrics service itself at https://sonar.digitalocean.com. Additionally, in order to allow the agent to update its self https://repos.sonar.digitalocean.com
Unfortunately, the IP addresses behind those domains are not guaranteed to be stable. In particular, the repo for automatic updates is backed by an external CDN.
You can find their current IP addresses using: dig +short sonar.digitalocean.com and dig +short repo.sonar.digitalocean.com on the command line.
Here is a currently working example:
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.