search

vercel / fun

ƒun - Local serverless function λ development runtime
Apache License 2.0
482 stars 26 forks source link

No way to set AWS_ACCESS_KEY_ID? #18

Closed dpeek closed 5 years ago

dpeek commented 5 years ago

I see there are a set of env vars we're not allowed to set, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY included. Problem is when calling AWS SDK from inside a function I'd like to not have to pass those from somewhere else (which matches what happens in production).

Is there some other way of passing these in? If not could there be? :)

TooTallNate commented 5 years ago

You can set them manually from within your lambda code before using the AWS SDK.

TooTallNate commented 5 years ago

We could also add a configuration option for this, patch welcome 👍

dpeek commented 5 years ago

Currently setting them through the SDK as suggested, but seems cleaner to remove this local conditional logic and just do what happens in production. Will take a stab at a patch.

TooTallNate commented 5 years ago

Fixed in b6796d82a5425506cd382206e56add591e8c25eb.