Skip to content

error for lambda

0

Enter image description here this is my error

  • From the error, it evident that there is a module "strands" that is being used. This module is missing. You need to either add a module with this name or correct the typo where it is referring to

asked a year ago173 views

3 Answers
0

Hello.

An import error is occurring.
What Lambda code are you using?
Judging from the error, there is no module called "strands" and the import failed.
If you can use Docker, I recommend creating a Lambda layer using the steps in the following document.
https://repost.aws/knowledge-center/lambda-layer-simulated-docker

EXPERT

answered a year ago

0

From the error, it evident that there is a module "strands" that is being used. This module is missing. You need to either add a module with this name or correct the typo where it is referring to

answered a year ago

-1

Based on the error message shown in your image, you're experiencing an "Access denied" error with an "UnknownError" message when trying to work with AWS Lambda.

This type of error typically indicates a permissions issue. Here are several potential causes and solutions:

  1. IAM Permissions: You may not have the necessary permissions to perform Lambda operations. Ensure your IAM user or role has appropriate Lambda permissions. You might need a policy that includes actions like lambda:*, logs:*, cloudwatch:*, and iam:PassRole.

  2. Service Control Policies (SCPs): If your AWS account is managed by AWS Organizations, there might be SCPs in place restricting Lambda operations, even if you have the appropriate IAM policies.

  3. Region Check: Verify you're in the correct AWS region where you intend to work with Lambda functions.

  4. Service Health: Check the AWS Service Health Dashboard to see if there are any ongoing issues with Lambda or IAM services in your region.

  5. Browser Issues: Try accessing Lambda from a different browser, in incognito mode, or from a different device to rule out any local issues.

  6. Trust Relationships: If you're using a specific execution role for Lambda, ensure the trust relationship is properly configured to allow Lambda to assume the role.

If you continue to experience this issue after checking these items, contacting AWS Support would be recommended as they can investigate account-specific issues that might be causing this problem.
Sources
Unknow Error when creating a Lambda Function | AWS re:Post

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.