What software does Cutover Connect™ require?
Cutover Connect™ requires Java 17+ runtime environment (JRE) to operate. Refer to the official Oracle Java download page for more information.
What hardware does Cutover Connect™ require?
The Cutover Connect™ server executable (‘JAR file’) requires approximately 2GB of disk space on execution to allow for log file generation, disk swap space and so on. Cutover recommends allocating at least 2GB of RAM to allow in-memory
caching, JRE environment loading and general memory management. We also recommend the following:
Are there any network or firewall requirements for using Cutover Connect™?
Cutover Connect™ will require outbound access to the internet to allow Cutover messages to be retrieved via ‘the Secure Channel’. Configure your firewall to allow outbound HTTP connections on port 443 to:
https://<subdomain>.cutover.com
https://<subdomain>.cutover.net
https://api.<subdomain>.cutover.com
https://api.<subdomain>.cutover.net
https://aws-proxy.cutover.com
https://aws-proxy.integrations.cutover.com
https://aws-proxy.dev-integrations.cutover.com
https://cutover-connect.integrations.cutover.com
Note: Always consult your Information Security and Networking teams to ensure your company security guidelines are followed correctly.
Does Cutover Connect™ support network throttling?
Cutover Connect™ does not have built-in network throttling. However, message processing is naturally limited by the design: Cutover Connect™ polls messages from SQS based on a configurable timer and processes them using a set number of threads (up to 10). This limits throughput without requiring external throttling.
Can Cutover Connect™ handle high volumes of messages from SQS?
Yes. Cutover Connect™ reads messages from the queue at controlled intervals. The polling frequency and number of processing threads are configurable, which prevents the system from becoming overwhelmed. If needed, additional limits can be added to further control how frequently Cutover Connect™ checks the queue.
Does Cutover Connect™ use a circuit breaker mechanism?
Yes. Cutover Connect™ supports circuit breaking on polling integrations. If a request does not receive a response, Cutover Connect™ will retry up to three times. After three unsuccessful attempts, the integration is marked as failed, and no further polling messages will be sent for that task.
Does Cutover Connect™ have a retry mechanism for HTTP calls?
Yes. When Cutover Connect™ makes HTTP calls, it will retry up to three times if there is an I/O exception (e.g. an unreachable endpoint). If a valid HTTP error is returned (like 401 Unauthorized or 404 Not Found), no retry will be attempted, as this is expected behavior.
