FAQ: Whitelisting IPs & Domains for Komodor

Introduction

When integrating Komodor with your infrastructure, some environments may have network security policies that require explicit whitelisting of external IP addresses and domains. To ensure seamless connectivity and functionality, customers may need to allow traffic to and from Komodor’s services. Below, we provide the necessary static IPs and domains that should be whitelisted to avoid any disruptions.

Static IPs for Production Tenant

For environments requiring static IPs for outbound communication, the following IP addresses should be whitelisted:

• Elastic IPs:
  • 44.212.240.150
  • 100.25.32.87
  • 23.22.93.59
• app.komodor.com:
  • 99.83.186.10
  • 75.2.72.226

These IPs are used for essential Komodor services, and whitelisting them ensures that your instance can properly communicate with Komodor’s backend systems.

Required Domains & Subdomains

Most of Komodor's functionality relies on our main domain (komodor.com) and a few specific subdomains. If your security policy requires domain-based whitelisting, please ensure the following are allowed:

• app.komodor.com (Komodor’s web application)
• gql.app.komodor.com (GraphQL API endpoint)
• api.komodor.com (REST API services)
• telemetry.komodor.com (Telemetry and monitoring services)

Whitelisting these domains allows proper access to Komodor’s services, enabling real-time debugging, event tracking, and automation capabilities.

Additional Considerations

• If your organization enforces strict firewall rules, ensure these IPs and domains are permitted for both inbound and outbound traffic.
• Changes to our static IPs or domains will be communicated through official channels and documented in our Help Center.

For further assistance, please reach out to Komodor Support.