如何获取Amazon Connect Lambda请求格式的正式Schema？相关文档未更新

Great question — I've run into this exact issue before when building integrations between Amazon Connect and Lambda. Let's break this down into actionable steps for both getting a working schema and finding official standardized documentation:

1. Capture a Real-World Payload (Quickest, Most Reliable Method) #

If you need the exact schema your Lambda will receive from Amazon Connect, nothing beats seeing a live request:

• Create a minimal test Lambda function that logs the entire incoming event parameter to CloudWatch. For example, in Node.js:

  exports.handler = async (event) => {
    console.log(JSON.stringify(event, null, 2));
    return { statusCode: 200 };
  };
  

• Configure your Amazon Connect instance to invoke this Lambda from a contact flow using the "Invoke Lambda function" block.
• Trigger a test call through your Connect instance (use the built-in test phone number in the Connect console to simulate a customer interaction).
• Check the Lambda's CloudWatch Logs — you'll find the full, structured payload that Connect sends, which you can use as a base for your schema.

2. Locate Official Standardized Format Resources #

You're correct that the general Lambda event mapping docs don't explicitly cover Amazon Connect, but there are official AWS resources that outline the request structure:

• Amazon Connect Integration Documentation: The official Connect docs have dedicated sections on Lambda integrations that detail the event structure field-by-field. Look for pages focused on invoking Lambda from Connect — these explain key fields like Details.ContactData.ContactId, Details.ContactData.CustomerEndpoint, and custom attributes set in your contact flow.
• Typed SDK Definitions: If you use a typed language like TypeScript, check AWS SDK type definitions (e.g., community-maintained packages like @types/amazon-connect-lambda) or the @aws-sdk/client-connect package. These include interfaces that mirror the Connect Lambda event structure, acting as a de facto schema.
• Serverless Sample Apps: AWS's Serverless Application Repository hosts pre-built apps for Connect + Lambda integrations. Many of these include schema definitions or type hints for incoming Lambda events, which you can use as a reference for standardized fields.

3. Generate a Formal JSON Schema #

If you need a machine-readable JSON Schema:

• Take the live payload you captured from CloudWatch.
• Use a JSON Schema generator tool (online or CLI-based) to convert the payload into a valid schema.
• Cross-reference the generated schema with official Connect docs to ensure required fields are marked correctly and optional fields are accounted for.

Note: AWS doesn't currently publish a standalone JSON Schema for Amazon Connect Lambda events, so combining real-world payloads with official documentation is the most reliable approach.

内容的提问来源于stack exchange，提问作者Chris Haddad