StartOutboundChatContact API failing

If you are invoking the API using API Gateway, you may get the error from this service, and not Connect. Check out this link and see if this is the case: https://gist.github.com/djm/15cf09b6b21c20332a602d3bca6b6d08

I understand you're experiencing issues with the StartOutboundChatContact API in Amazon Connect. Let's address this problem step by step:

1. The "AuthorizerConfigurationException" error you're seeing in CloudTrail suggests that there's an issue with the permissions or configuration of the IAM role or user making the API call.

2. You're correct that there isn't a specific action called "connect:StartOutboundChatContact" in IAM permissions. The StartOutboundChatContact API is actually part of the broader Amazon Connect service permissions.

3. While using "connect:*" in your IAM policy should theoretically grant all Connect permissions, it's possible that this broad permission isn't being applied correctly or there are other factors at play.

To resolve this issue, I recommend the following steps:

1. Instead of using the broad "connect:*" permission, try explicitly adding the "connect:StartOutboundChatContact" action to your IAM policy. Even though this isn't listed as a separate action, it may be required for the API to work correctly.

2. Ensure that your IAM role or user has the necessary permissions to access other required resources. The StartOutboundChatContact API might require access to related services or resources.

3. Double-check that you're using the correct AWS region and that your IAM permissions are set up in the same region as your Amazon Connect instance.

4. Verify that your Amazon Connect instance has the necessary configurations to support outbound chat contacts, particularly SMS chats which are currently the only supported type for this API.

5. If you continue to face issues, you may need to contact AWS Support for further assistance. They can provide more detailed insights into the specific permissions and configurations required for your use case.

Remember, when working with AWS APIs, it's always a good practice to start with the principle of least privilege and gradually add permissions as needed, rather than using broad permissions like "connect:*".

If these steps don't resolve your issue, please provide more details about your specific setup and any error messages you're receiving for further assistance.
Sources
StartOutboundChatContact - Amazon Connect
StartOutboundChatContact - Amazon Connect
Troubleshooting AWS CloudTrail identity and access - AWS CloudTrail