Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Categories Performance
Created by Guest
Created on Jan 7, 2026

Request for Multi‑Endpoint / Automatic Failover Support for S3 IO Exit in Connect:Direct

During multiple production runs, we observed intermittent S3 transfer failures in Connect:Direct. The failures are inconsistent, and not all transfers are affected. Our internal teams (SRE, Storage/S3, and Network) are continuing deeper analysis, but initial evidence points to a lack of response from the S3 endpoint for approximately one minute during certain intervals.

We currently configure Connect:Direct’s S3 IO Exit to use a single s3.endpointUrl, which points to a load balancer. We suspect the load balancer may be contributing to the connection drops. As part of troubleshooting, we plan to test using direct IPs instead of the LB.

This raised a critical question:
Does Connect:Direct support defining multiple S3 endpoints (Primary + Secondary) so that CD can automatically fail over when the primary endpoint is unresponsive?

What is your industry? Financial Markets
How will this idea be used?

This enhancement is critical for the following reasons:

  • Intermittent failures occur when the S3 endpoint (or load balancer in front of it) does not respond.

  • Without endpoint failover, Connect:Direct fails the entire transfer instead of retrying with a secondary endpoint.

  • High‑volume environments (like ours) require resilience and redundancy to avoid disruptions.

  • Manual updates to initparm.cfg during outages are operationally risky and not feasible.

  • Other CD components (e.g., Netmap) already support primary/alternate communication parameters; extending similar capability to the S3 IO Exit would significantly improve reliability.