From Bright Pattern Documentation
< 5.19:Amazon-aws-lambda-integration-guide‎ | Configuration
Revision as of 04:01, 29 May 2024 by BpDeeplTranslateMaintenance (talk | contribs) (Updated via BpDeleteTranslateTags script)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
• 5.19 • 5.8

Troubleshooting

In testing your Amazon AWS Lambda integration, you might experience some difficulties. Here are some common problems and how you can resolve them.

Invalid Credentials

When configuring your Amazon AWS Lambda integration account, if you receive the “Account credentials are invalid” error message when clicking the Test Connection button, please review your Amazon Identity Access Manager (IAM) group policies. You will need to verify that the IAMReadOnlyAccess policy is included in your configured group.


Ensure you have the correct policies configured in IAM


AWS Lambda Block Failure

In your scenarios, if you find that you are unable to invoke the Amazon AWS Lambda function specified in the AWS Lambda block, you can add either an EMail block or an Internal Message block on the Failed conditional exit.


The Failed conditional exit


In either block, you will add the variables $(integrationResultsBody) and/or $(integrationResultsCode). These variables pass the exact HTTP response information the system is receiving. Note that the AWS Lambda block’s Failed conditional exit will be taken if it receives anything other than a 200 (i.e., successful) response.


Use HTTP response info to help determine what went wrong
< Previous