Loading

AWS SDK- Default AWS Credentials Provider Chain

게시 일자: Feb 28, 2025
과업

AWS SDK- Default AWS Credentials Provider Chain

단계

QUESTION

Need help on a customer case. AWS S3 connector for not to put access key and secrets in configs cross-account access using AssumeRole
following article written in 2018 says works only for on-premise servers.
https://help.salesforce.com/s/articleView?id=How-to-use-Default-AWS-Credentials-Provider-Chain-in-S3-connector&type=1&language=en_US
tryDefaultAWSCredentialsProviderChain=“true”
It is blocker for customer to move mule apps to cloud hub. Does it work now for app in cloudhub or it does not and same as earlier?

ANSWER

The article written with tryDefaultAWSCredentialsProviderChain="true" purpose is to not show clear text credentials in the XML file.
As an alternative, you can also use secure properties configuration for users to not see them using https://docs.mulesoft.com/mule-runtime/4.3/secure-configuration-properties.

Your use case is specific to AWS SDK and a mule is wrapper code around AWS SDK. To achieve what you need, you have to review AWS documentation. Please check the following AWS documentation and to make it work in the cloud hub you have to run your application with java system properties configuration.

Check this doc https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html

To set up it on cloud hub follow these steps with Java system properties :

Go to Settings of your application on cloud hub
Select Properties tab
Add these 2 properties with your credentials — aws.accessKeyId and aws.secretKey

ADDITIONAL INFORMATION

It is an infrastructure limitation. Cloud hub worker use mulesoft specific credentials and can not assume cross-account customer role
Knowledge 기사 번호

001116323

 
로드 중
Salesforce Help | Article