Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. 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 Under review
Workspace App Connect
Created by Guest
Created on May 15, 2025

Copy file to S3 without ACE required to pass the whole content of the file

In the current implementation of S3 request node, for transferring file from one location to S3 or from S3 to target location (ex: S3 to GCP Storage, GCP Storage to S3 or Any files created in ACE File storage to S3), the file content needs to be passed as part of the JSON schema required for S3. Due to the requirement to copy the whole file content, it is challenging and memory requirement is high depends on the file size, hence not suitable to move large files to S3 using S3 request node.  

Hence it will be beneficial, if S3 request node have an option to move the file without copying the whole content in the JSON and, only through the source location (GCS or Folder location) and target S3 location. This will help to utilize the S3 request node irrespective of the file size and enhance the usage of ACE across multiple use cases

Idea priority High
  • Guest
    May 22, 2025

    Additional input:

    One of the major use case related to S3 interaction is, for any batch process/file based process, S3 is primarily used as the file storage for log purpose (logging the source file into S3 bucket for troubleshoot purpose). As part of that, the file will be available in the ACE internal file storage (/home/aceuser/generic/<folder path>) and have to move it to S3 before the actual process. Also the vice versa, for any reprocessing of the files from S3, the files need to be pulled from S3 to ACE internal storage (/home/aceuser/generic/<folder path>). For these kind of usecase, it will be beneficial if S3 connector can able to poll the file from the source path (ACE container) and push the file to S3/Pull the files from S3.

    Source path: /home/aceuser/generic/<folder path>

    target path: S3 bucket

    vice versa

    Thanks,

    Santhosh Ramanathan