- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
1. Is allowing static FQDN (https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound-traffi..." the best approach or do we still need to work on allowing the Wildcard domains as mentioned in the link "Outbound Traffic &
Port Requirements".
2. Idira documentation (https://docs.cyberark.com/setup/latest/en/content/ispss-deployment/deployment/deploy-outbound_traffi...) mentions to open *.idap.co but there is no specific endpoint on this domain in the Static FQDN doc link mentioned above neither in the attached network requirement file attached to this case.
Can we ignore *.idap.co considering if we allow only the static FQDN's?
1. We strongly recommend Dynamic Configuration using Wildcard domains. While static configuration is supported as a secondary fallback, wildcard domain allow listing is the preferred architectural pattern for SaaS deployments.
Relying strictly on static FQDNs carries a high risk of future service disruption.
Here is why:
Elastic SaaS Architecture: Idira SaaS continually updates, scales microservices, and adds new storage endpoints (S3 buckets, CloudFront distributions). Hardcoded static lists require manual updating whenever underlying infrastructure scales.
AWS IoT Core Cross-Region Routing: Services such as Connector Management and Session Interactive Agents (SIA) rely on AWS IoT Core brokers for real-time channels. Even if a tenant primary region is us-east-1, AWS IoT brokers utilize multi-region fallback mechanisms (e.g., routing traffic to us-west-2 or global endpoints during high traffic or failover scenarios). A rigid static list generated at a single point in time will block these secondary endpoints during routing shifts.
2. You do not need to allow *.idap.co for a static configuration. The official connector prerequisite script polls the Idira backend APIs and dynamically outputs the exact requirements for your specific tenant.