Views:

Diagnose connectivity failures between the Claude Compliance Collector Lambda functions and AI Guard or the Anthropic Compliance API using CloudWatch Logs.

Procedure

  1. Check the relevant CloudWatch log group for exhausted_retries events where error_class is RateLimitedError and error_message starts with Network error on:
    • /aws/lambda/claude-compliance-collector-process-chat — Check for both AI Guard and Anthropic connectivity errors during chat processing.
    • /aws/lambda/claude-compliance-collector-list-activities — If the Anthropic Compliance API is unreachable, the error often surfaces here before ProcessChat sees a problem.
    The error_message field indicates the source of the issue:
    • Network error on POST https://<your-ai-guard-host>/... — The Lambda cannot reach the AI Guard endpoint.
    • Network error on GET https://api.anthropic.com/... — The Lambda cannot reach the Anthropic Compliance API.
    Note
    Note
    Plain 429 rate-limit errors show error_message starting with Rate limited (429) on, not Network error on. If you do not see Network error on, the issue is not a connectivity problem.