Overview
In some scenarios, systems that our inspectors integrate with have IP restrictions in place. When an inspector is assigned to an On-Demand agent, this can present a challenge because On-Demand agents are hosted within AWS and utilize dynamic IP addresses from a shared IP pool.
Solution: Using Self-Hosted Agents
To bypass this limitation, we recommend using Self-Hosted Agents. These agents can be installed locally on servers or workstations and, in most cases, support the majority of Liongard's inspectors.
Steps to Implement
Install a Self-Hosted Agent
Download and install the Self-Hosted Agent on a server or workstation within your network.
Reassign Inspectors
Once the Self-Hosted Agent is installed, reassign your inspector(s) to use the new agent.
Allow the Agent’s IP Address
Identify the public or internal IP address of the device hosting the Self-Hosted Agent.
Add this IP address to the allow list of the target system's IP restrictions to ensure successful communication.
Additional Considerations
Ensure the Self-Hosted Agent remains online and accessible for the assigned inspector to function properly.
If the agent’s host device has a dynamic public IP, consider using a static IP or a VPN solution to maintain consistent connectivity.
Verify firewall and network settings to avoid blocking the necessary traffic between the inspector and the target system.
By following these steps, you can successfully overcome IP restriction issues and maintain seamless integration with Liongard's inspectors.