You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our mulesoft deployed apps run on aws VMs whose node instance profile has rights to access the AWS secrets.
We just make sure the node-instance-profile is able to pull secrets out of the AWS secrets manager and we are good. Those VMs do not use credential or config profile files under the home .aws dirctories.
How should we setup automation-credentials.properties when using node instance profile. Since credential and config profiles are not used, how can we just get the app to use what ever credentials the node instance currently has.
The text was updated successfully, but these errors were encountered:
hectoralicea
changed the title
how do you setup automation-credentials.properties when using MFA or node instance profile
how do you setup automation-credentials.properties when using node instance profile
Jul 24, 2023
Our mulesoft deployed apps run on aws VMs whose node instance profile has rights to access the AWS secrets.
We just make sure the node-instance-profile is able to pull secrets out of the AWS secrets manager and we are good. Those VMs do not use credential or config profile files under the home .aws dirctories.
How should we setup automation-credentials.properties when using node instance profile. Since credential and config profiles are not used, how can we just get the app to use what ever credentials the node instance currently has.
The text was updated successfully, but these errors were encountered: