Cutover Connect™ FAQS

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: ‍

Linux (preferred) or Windows Server (Windows Server 2019+) host with
Java 17 installed - as a container, VM or dedicated hardware
environment as a minimum

2GB RAM and 5GB disk space (in addition to host system requirements)

Firewall access to enable Cutover Global Proxy (AWS) HTTPS requests
on port 443

Ability to download zip files from Cutover Core (required to download the
Cutover Connect package™

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:

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.

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.

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.

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.

The name of your Cutover Connect™ project is used to generate the AWS infrastructure (Cutover Transform) and appears anywhere an integration or data source is defined. Use a name that clearly describes the purpose or function of the project such as:

CMDB

Ingest pipelines

Connect Based Automations

Automated Workflows

Ready for Business Automations

Avoid vague or generic names such as:

test-project

connect v73.4

jksdkjsjk

new connect download

my integration