Enable alternative authentication methods for S3 buckets

We’re currently working with a client on an opportunity that impacts multiple products, including watsonx.data, CP4D, Data Virtualization, and Data Gate. The client is eager to adopt our lakehouse solution but has stringent security requirements that necessitate alternative authentication methods for accessing S3 buckets.Background:

We are currently collaborating with the client on a PoC to showcase the capabilities of our lakehouse solution.
The client is highly restrictive with IAM accounts and API Keys. While these methods might suffice for the PoC, they are not acceptable for their production environment.
The client has suggested associating EC2 instances with a user/group that can access the bucket directly.
They are also inquiring about the possibility of utilizing Security Token Service (STS) for temporary credentials.

Request:
Given the client’s requirements and the potential to enhance our product offerings, I would like to request that the development team consider supporting additional authentication methods for S3 buckets. Specifically:

Integrating AWS Security Token Service (STS) to provide temporary, limited-privilege credentials for accessing S3 resources.
(Alternative authentication methods that offer enhanced security compared to access and secret keys.)

Needed By

Quarter

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Enable alternative authentication methods for S3 buckets