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
I was also wondering if we could rely on IAM Roles to execute the AWS API calls, in my case I'm trying to run node-red in a lambda and use IAM Role of the lambda to send a message SQS.
I'll take a look, and if possible, I'll raise a PR so we can start the discussion.
I was also wondering if we could rely on IAM Roles to execute the AWS API calls, in my case I'm trying to run node-red in a lambda and use IAM Role of the lambda to send a message SQS. I'll take a look, and if possible, I'll raise a PR so we can start the discussion.
From a quick review, during the execution of a Lambda the env vars: AWS_ACCESS_KEY, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN are available, and they are generated from the Execution role attached to the lambda. Which means we can use those vars on configuration, no need to change the code. 👍
When running a node red instance inside ECS, it would be handy to use the ECS task credentials rather than setting up a credentials node.
https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-credentials-node.html
The text was updated successfully, but these errors were encountered: