Skip to content
This repository has been archived by the owner on Mar 6, 2022. It is now read-only.

Can I use an EC2 IAM attached role? #7

Closed
nodesocket opened this issue Jun 27, 2019 · 2 comments
Closed

Can I use an EC2 IAM attached role? #7

nodesocket opened this issue Jun 27, 2019 · 2 comments
Labels

Comments

@nodesocket
Copy link

When I run:

awslambdaproxy run us-west-1,us-west-2,us-east-1,us-east-2

Getting:

Must specify environment variable AWS_ACCESS_KEY_ID

The EC2 instance should already have the policies needed via the attachd IAM role.

@dan-v
Copy link
Owner

dan-v commented Jun 27, 2019

Hey @nodesocket. It can run with an IAM profile, but there is a check preventing it from running currently: https://github.com/dan-v/awslambdaproxy/blob/master/cmd/awslambdaproxy/cmd/run.go#L70. With that removed it should work fine.

I haven't updated this project in quite a while and it needs a little love. Building from source appears to be problematic at the moment (needs to move to go modules and go-bindata appears to have been abandoned). I'll leave this issue open and try to fix it and the build process when I get a chance. Also open to any PRs.

@dan-v dan-v added the bug label Jun 27, 2019
@dan-v
Copy link
Owner

dan-v commented Jul 3, 2019

Pushed new release that removes this hardcoded environment variable check.

@dan-v dan-v closed this as completed Jul 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants