@karmaniverous/smoz
    Preparing search index...
    BaseEventTypeMap: {
        alb: ALBEvent;
        cloudfront: CloudFrontRequestEvent;
        "cloudwatch-logs": CloudWatchLogsEvent;
        "cognito-userpool": CognitoUserPoolTriggerEvent;
        dynamodb: DynamoDBStreamEvent;
        eventbridge: EventBridgeEvent<string, unknown>;
        firehose: FirehoseTransformationEvent;
        http: APIGatewayProxyEventV2;
        kinesis: KinesisStreamEvent;
        rest: APIGatewayProxyEvent;
        s3: S3Event;
        ses: SESEvent;
        sns: SNSEvent;
        sqs: SQSEvent;
        step: { Payload?: unknown; [key: string]: unknown };
    }

    Canonical base event map type (schema‑first). Extend the schema in your App.

    Type Declaration

    • alb: ALBEvent
    • cloudfront: CloudFrontRequestEvent
    • cloudwatch-logs: CloudWatchLogsEvent
    • cognito-userpool: CognitoUserPoolTriggerEvent
    • dynamodb: DynamoDBStreamEvent
    • eventbridge: EventBridgeEvent<string, unknown>
    • firehose: FirehoseTransformationEvent
    • http: APIGatewayProxyEventV2
    • kinesis: KinesisStreamEvent
    • rest: APIGatewayProxyEvent
    • s3: S3Event
    • ses: SESEvent
    • sns: SNSEvent
    • sqs: SQSEvent
    • step: { Payload?: unknown; [key: string]: unknown }

      Step Functions → Lambda (Service Integration: Lambda Invoke)

      When Step Functions invokes Lambda via the AWS SDK integration (e.g., "arn:aws:states:::lambda:invoke"), the event received by the Lambda handler is an object that wraps the original input under a "Payload" key. The Payload is already parsed JSON.

      Notes:

      • We accept additional keys (e.g., StatusCode/ExecutedVersion in some patterns) via passthrough.
      • For the common “request/response” integration where Step Functions passes state directly, apps can still treat the event via their own app-local event map if needed.