Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Allow credentials to be supplied by ECS container #77

Open
bonnydeal opened this issue Sep 7, 2021 · 3 comments
Open

Comments

@bonnydeal
Copy link

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

@Daniel-t
Copy link
Owner

Sounds reasonable, will investigate when time permits

@loe-lobo
Copy link

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.

@loe-lobo
Copy link

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. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants