Skip to content
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.

Allow monitoring services access to Spatial CIMIS servers #61

Open
gjscheer-ucd opened this issue May 8, 2019 · 0 comments
Open

Allow monitoring services access to Spatial CIMIS servers #61

gjscheer-ucd opened this issue May 8, 2019 · 0 comments
Assignees

Comments

@gjscheer-ucd
Copy link
Collaborator

gjscheer-ucd commented May 8, 2019

Current UCD GOES-R monitoring strategy is documented here. To recreate this strategy at DWR these firewall rules to allow remote monitoring service to access ports 22, 80 and 443 for the following Spatial CIMIS servers are required:

source IP port(s) protocol destination IP host
see whitelist 22,80,443 TCP see "Monitoring" in request log dev
see whitelist 22,80,443 TCP see "Monitoring" in request log testing
see whitelist 22,80,443 TCP see "Monitoring" in request log prod
see whitelist 22,80,443 TCP see "Monitoring" in request log W Sac dsp-box
see whitelist 22,80,443 TCP see "Monitoring" in request log W Sac grb-box

Must know public facing IPs for all spatial cimis servers.

Remote monitoring service is Uptime Robot. IP's to white list are listed here:
https://uptimerobot.com/locations.php
https://uptimerobot.com/inc/files/ips/IPv4.txt

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants