Network Requirements
Network configuration for Keeper Automator
Keeper Automator can be deployed many different ways - on prem, cloud or serverless.
Data Flow Diagram
In order to route requests to the instance, you need to update your public DNS with the IP address of the container service or instance.
- Create DNS A-record pointing to the public IP
- In the Security Group inbound traffic rules, open the port from the Keeper servers per below (based on your data center). Replace 443 with the port that you have configured in your deployment, if different.
In your firewall inbound traffic rules, set one of following rulesets:
For US Data Center Customers:
- Inbound TCP port 443 from 54.208.20.102/32
- Inbound TCP port 443 from 34.203.159.189/32
US / GovCloud Data Center Customers:
- Inbound TCP port 443 from 18.252.135.74/32
- Inbound TCP port 443 from 18.253.212.59/32
For EU / Dublin Data Center Customers:
- Inbound TCP port 443 from 52.210.163.45/32
- Inbound TCP port 443 from 54.246.185.95/32
For AU / Sydney Data Center Customers:
- Inbound TCP port 443 from 3.106.40.41/32
- Inbound TCP port 443 from 54.206.208.132/32
For CA / Canada Data Center Customers:
- Inbound TCP port 443 from 35.182.216.11/32
- Inbound TCP port 443 from 15.223.136.134/32
For JP / Tokyo Data Center Customers:
- Inbound TCP port 443 from 54.150.11.204/32
- Inbound TCP port 443 from 52.68.53.105/32
In addition, you may want to allow traffic from your office network (for the purpose of testing and health checks).
Make sure to create a rule for each IP address listed based on your Keeper geographic data center region.
Last modified 3mo ago