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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
We are using Dell EMC infrastructure, but we have successfully authenticated to it from the Dashboard using the AWS S3 authentication type, so it would be great if you could just open up the possibility of connecting to internal S3 using this type if desired without having to implement all the different provider auth mechanisms?
Also noting here duplicate idea https://integration-development.ideas.ibm.com/ideas/CIP-I-307
Thank you for taking the time to raise this request, which we are moving to the status of Future Consideration. For the benefit of future readers, it would be good to know which specific S3 provider is preferred. Unfortunately although S3 is fairly well established in the industry now, there is no neutral implementation standard defined. The key difference between most S3 provider implementations is the authentication mechanism - every provider typically deploys their own auth mechanism which is why we currently have only pursued support for AWS and IBM - although there can also be client API differences too. This is something we would like to address in future and the business priority which is applied will depend on community feedback.