Lambda function deployment Issues and bedrock error

It seems you're experiencing multiple issues with your AWS services, specifically with Lambda function deployment and Bedrock model invocation. Let's address these issues one by one:

For the Lambda function deployment issue:

The "UnknownError" you're encountering when trying to deploy Lambda functions can have several causes. First, ensure you're in the correct AWS region where your Lambda functions were originally created, as they are region-specific. It's also possible that there might be a temporary block on your account due to a suspected malicious access attempt, which can cause functions to become temporarily inaccessible.

Even though you mentioned no changes to permissions, it's worth double-checking that your account has the necessary IAM permissions to access and deploy Lambda functions. Insufficient permissions can lead to "UnknownError" messages. You should also check the AWS Service Health Dashboard to see if there are any ongoing issues or outages with Lambda in your region.

If the issue persists, try accessing your Lambda functions from a different browser or device to rule out any local issues. If you still can't resolve the problem, it's recommended to contact AWS Support. You can open a case under "Account and billing" which can be done free of charge. They can investigate any account-specific issues that might be causing this problem.

Regarding the Bedrock error:

The "ValidationException" error you're receiving when trying to invoke a Bedrock model suggests there might be an issue with permissions or configuration. To resolve this, you need to ensure that your Bedrock agent has the necessary permissions to invoke Lambda functions.

To fix this, you should add a resource-based policy statement on the Lambda function:

1. Go to your Lambda function in the AWS console
2. Select the "Configuration" tab
3. Choose "Permissions" from the menu
4. Scroll down to "Resource-based Policy Statements" and click "Add Permissions"
5. Select "AWS Service" and choose "Other" from the Service dropdown
6. Enter a Statement ID (can be anything)
7. Set the Principal to "bedrock.amazonaws.com"
8. Enter your Bedrock Agent's ARN as the Source ARN
9. Select "lambda:InvokeFunction" as the Action
10. Save the changes

This should grant the necessary permissions for Bedrock to invoke your Lambda function.

If you continue to experience issues after trying these solutions, it would be advisable to contact AWS Support for further assistance, as there might be account-specific factors at play.
Sources
Not able to see my lambda functions | AWS re:Post
Error when Bedrock agent invoke lambda | AWS re:Post