-
Notifications
You must be signed in to change notification settings - Fork 178
AmazonIdentityManagementException when deploying a Lambda function #97
Comments
Solved by seting the default region to US East (Virginia) in Eclipse preferences: Window -> Preferences -> AWS Toolkit -> Regions. |
Same issue to #94. The fix will be included in the next release. |
This fix has been included in the release. Thanks for the request. |
I am also having the same issue even after changing the region to US East (Virginia) here: Window -> Preferences -> AWS Toolkit -> Regions. Can you help me find out what's the problem this time? |
I am also facing same issue even after changing the region to US East (Virginia) |
Am also facing same issue even after chaning to US EAST/N Virginia |
Hi, @Tsaeeds @YugandharaP @prabhakar747 , Still couldn't reproduce this issue. Are you using the latest version of the Toolkit? You can find out the plugin version through Eclipse -> About Eclipse -> Installation Details -> Installed Software -> Filter by typing AWS. |
I installed the AWS Toolkit for Eclipse and created a Lambda project without issues, but I can't deploy my code from Eclipse directly to a Lambda function on AWS. All my AWS services are on the us-east/virginia region.
Whem I select "upload function to aws lambda", on the "Select Target Lambda function" screen, I can see and select an existing function (which resides on us-east/virginia).
On the next screen ("Function Configuration"), I get the following error: "Failed to load iam role in US East (Virginia): com.amazonaws.services.identitymanagement.model.AmazonIdentityManagementException: Credential should be scoped to a valid region, not 'us-west-2'. (Service: AmazonIdentityManagement; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: )."
I get the same error if I randomly change the "Lambda Handler and Target Region" on the "upload function to aws lambda" screen.
Is there a configuration problem with my setup? What is causing this error?
The text was updated successfully, but these errors were encountered: