Data action returns a 403 error


Note: This article applies to the AWS Lambda data actions integration.

A data action returns a 403 error. 

  • The AWS Lambda function that you are trying to invoke does not exist.
    • Create an AWS Lambda function in your AWS account. Then grant access to this AWS Lambda function in a policy associated with the role that you set under the integration configuration in PureCloud. 
  • The policy in your AWS account does not grant access to the correct AWS Lambda function.
    • Update the policy in your AWS account to grant invokeFunction access to the AWS Lambda function that you want your AWS Lambda data actions integration to call.
  • The policy that you attached to your role does not grant access to your AWS Lambda function. 
    • Add the policy to the role in your AWS account that grants access to an AWS Lambda function. 
  • The account ID set on the role in your AWS account is not PureCloud’s production AWS account ID.
    • Update the account ID on the role in your AWS account to 765628985471.
  • The external ID set on the role in your AWS account is not a PureCloud organization ID.
    • Update the external ID on the role in your AWS account. This role is the same role that you set in the integration configuration in PureCloud.

For more information, see Create IAM resources and Add a data actions integration.

For more information about the integration, see About the AWS Lambda data actions integration.