Closed wsingleton closed 3 years ago
The permissions do not come from the role/policies defined in the template.yaml when running locally since the toolkit can't assume those roles (Trust relationship forbids it).
The local lambda gets its permissions from the selected profile in the toolkit (Under the AWS Connection tab of the run config)
Does that role have permission?
It was set to the wrong region, I had overlooked that tab. I appreciate the help! I'll close this issue.
Describe the bug Not entirely sure if this is a bug or a misconfiguration on my part, but I cannot seem to successfully locally launch a Lambda function (written in Java 8) that is communicating with a DynamoDB table. I've included below, the files and configurations to a sample project that should recreate the issue.
Expected behavior I should be able to deploy this Lambda function locally using the AWS Toolkit for IntelliJ
Screenshots Project Files:
./pom.xml
./template.yml
./src/main/java/com/example/GetBooksHandler.java
./src/main/java/com/example/Book.java
./src/main/java/com/example/BookResponse.java
Local Run Output:
Your Environment
Additional context
template.yml
has the appropriate permissions to access the DynamoDB table