From d0f6b1d3202044805412b2daf3867f46b9c052d5 Mon Sep 17 00:00:00 2001 From: Bruno Belotti Date: Wed, 22 Feb 2017 23:12:35 +0000 Subject: [PATCH] Profile in place with the invoke local Add a section with a warning about the AWS profile/IAM role `invoke local` (to alleviate issue #2903) --- docs/providers/aws/guide/credentials.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/providers/aws/guide/credentials.md b/docs/providers/aws/guide/credentials.md index e803d0210..70fb3575c 100644 --- a/docs/providers/aws/guide/credentials.md +++ b/docs/providers/aws/guide/credentials.md @@ -147,3 +147,10 @@ custom: dev: devProfile prod: prodProfile ``` + +#### Profile in place with the 'invoke local' command + +**Be aware!** Due to the way AWS IAM and the local environment works, if you invoke your lambda functions locally using the CLI command `serverless invoke local -f ...` the IAM role/profile could be (and probably is) different from the one set in the `serverless.yaml` configuration file. +Thus, most likely, a different set of permissions will be in place, altering the interaction between your lambda functions and others AWS resources. + +*Please, refer to the `invoke local` CLI command documentation for more details.*