Public IPs Whitelisting (all customers)
Keragon adopts a high-security approach for all customers, and has a fixed set of IP addresses that all Keragon workflow traffic emerges from.
If you have private resources (i.e. internal apps, self-hosted services, own databases) that you'd like to have as part of your workflow automations or you have particular information security requirements (i.e. on-prem data residency), feel free to whitelist with your firewall the following Keragon public static IPs:
US region
- 18.214.155.250
- 34.197.3.75
- 54.225.183.38
This is the simplest & most popular on-prem deployment option for infrastructure hosted on either own physical premises or public cloud providers.
​
After you whitelist these specific IP addresses, you help ensure that you're only receiving incoming requests from Keragon and not exposing your services to the entire internet.
AWS On-prem Connection (Enterprise customers only)
If you're hosting private assets on AWS that want them integrated with Keragon's workflow automations, we have the following options available for those that have specific security needs (i.e. unique execution environments or data stored locally):
-
Using AWS Transit Gateway Attachment, you can consider a Keragon-owned VPC to become a spoke in your network
-
Using AWS Transit Gateway Peering, you can peer your Transit Gateway with one owned by Keragon
-
Using AWS PrivateLink, you can create an Endpoint Service
-
Using AWS VPC Peering, you can set up strict ACL rules to ensure secure connectivity with Keragon
Please note that these AWS on-prem options are only offered to our Enterprise clients and you should reach out to Keragon support for further discussions.