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)
This commit is contained in:
Bruno Belotti 2017-02-22 23:12:35 +00:00 committed by GitHub
parent fb057d12c8
commit d0f6b1d320

View File

@ -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.*