AppSync Events - Powertools for AWS Lambda (.NET) (original) (raw)

Event Handler for AWS AppSync real-time events.

stateDiagram-v2
    direction LR
    EventSource: AppSync Events
    EventHandlerResolvers: Publish & Subscribe events
    LambdaInit: Lambda invocation
    EventHandler: Event Handler
    EventHandlerResolver: Route event based on namespace/channel
    YourLogic: Run your registered handler function
    EventHandlerResolverBuilder: Adapts response to AppSync contract
    LambdaResponse: Lambda response

    state EventSource {
        EventHandlerResolvers
    }

    EventHandlerResolvers --> LambdaInit

    LambdaInit --> EventHandler
    EventHandler --> EventHandlerResolver

    state EventHandler {
        [*] --> EventHandlerResolver: app.resolve(event, context)
        EventHandlerResolver --> YourLogic
        YourLogic --> EventHandlerResolverBuilder
    }

    EventHandler --> LambdaResponse

Key Features¶

• Easily handle publish and subscribe events with dedicated handler methods
• Automatic routing based on namespace and channel patterns
• Support for wildcard patterns to create catch-all handlers
• Process events in parallel or sequentially
• Control over event aggregation for batch processing
• Graceful error handling for individual events

Terminology¶

AWS AppSync Events. A service that enables you to quickly build secure, scalable real-time WebSocket APIs without managing infrastructure or writing API code. It handles connection management, message broadcasting, authentication, and monitoring, reducing time to market and operational costs.

Getting started¶

Tip: New to AppSync Real-time API?

Visit AWS AppSync Real-time documentation to understand how to set up subscriptions and pub/sub messaging.

Required resources¶

You must have an existing AppSync Events API with real-time capabilities enabled and IAM permissions to invoke your Lambda function.

Getting started with AppSync Events

AppSync request and response format¶

AppSync Events uses a specific event format for Lambda requests and responses. In most scenarios, Powertools for AWS simplifies this interaction by automatically formatting resolver returns to match the expected AppSync response structure.

AppSync payload requestAppSync payload responseAppSync payload response with error

Events response with error¶

When processing events with Lambda, you can return errors to AppSync in three ways:

• Item specific error: Return an error key within each individual item's response. AppSync Events expects this format for item-specific errors.
• Fail entire request: Return a JSON object with a top-level error key. This signals a general failure, and AppSync treats the entire request as unsuccessful.
• Unauthorized exception: Raise the UnauthorizedException exception to reject a subscribe or publish request with HTTP 403.

Resolver¶

Important

When you return Resolve or ResolveAsync from your handler it will automatically parse the incoming event data and invokes the appropriate handler based on the namespace/channel pattern you register.

You can define your handlers for different event types using the OnPublish(), OnPublishAggregate(), and OnSubscribe() methods and their Async versions OnPublishAsync(), OnPublishAggregateAsync(), and OnSubscribeAsync().

Publish events - Class library handlerPublish events - Executable assembly handlersSubscribe to events

Advanced¶

Wildcard patterns and handler precedence¶

You can use wildcard patterns to create catch-all handlers for multiple channels or namespaces. This is particularly useful for centralizing logic that applies to multiple channels.

When an event matches with multiple handlers, the most specific pattern takes precedence.

Wildcard patterns

Supported wildcard patterns

Only the following patterns are supported:

• /namespace/* - Matches all channels in the specified namespace
• /* - Matches all channels in all namespaces

Patterns like /namespace/channel* or /namespace/*/subpath are not supported.

More specific routes will always take precedence over less specific ones. For example, /default/channel1 will take precedence over /default/*, which will take precedence over /*.

Aggregated processing¶

Aggregate Processing

OnPublishAggregate() and OnPublishAggregateAsync(), receives a list of all events, requiring you to manage the response format. Ensure your response includes results for each event in the expected AppSync Request and Response Format.

In some scenarios, you might want to process all events for a channel as a batch rather than individually. This is useful when you need to:

• Optimize database operations by making a single batch query
• Ensure all events are processed together or not at all
• Apply custom error handling logic for the entire batch

Aggregated processing

Handling errors¶

You can filter or reject events by raising exceptions in your resolvers or by formatting the payload according to the expected response structure. This instructs AppSync not to propagate that specific message, so subscribers will not receive it.

Handling errors with individual items¶

When processing items individually with OnPublish() and OnPublishAsync(), you can raise an exception to fail a specific item. When an exception is raised, the Event Handler will catch it and include the exception name and message in the response.

Error handling individual itemsError handling individual items AsyncError handling individual items response

Handling errors with batch of items¶

When processing batch of items with OnPublishAggregate() and OnPublishAggregateAsync(), you must format the payload according the expected response.

Error handling batch itemsError handling batch items AsyncError handling batch items response

Raising UnauthorizedException will cause the Lambda invocation to fail.

You can also reject the entire payload by raising an UnauthorizedException. This prevents Powertools for AWS from processing any messages and causes the Lambda invocation to fail, returning an error to AppSync.

• When working with publish events Powertools for AWS will stop processing messages and subscribers will not receive any message.
• When working with subscribe events the subscription won't be established.

Rejecting the entire request

Accessing Lambda context and event¶

You can access to the original Lambda event or context for additional information. These are accessible via the app instance:

Accessing Lambda context

Event Handler workflow¶

Working with single items¶

sequenceDiagram
    participant Client
    participant AppSync
    participant Lambda
    participant EventHandler
    note over Client,EventHandler: Individual Event Processing (aggregate=False)
    Client->>+AppSync: Send multiple events to channel
    AppSync->>+Lambda: Invoke Lambda with batch of events
    Lambda->>+EventHandler: Process events with aggregate=False
    loop For each event in batch
        EventHandler->>EventHandler: Process individual event
    end
    EventHandler-->>-Lambda: Return array of processed events
    Lambda-->>-AppSync: Return event-by-event responses
    AppSync-->>-Client: Report individual event statuses

Working with aggregated items¶

sequenceDiagram
    participant Client
    participant AppSync
    participant Lambda
    participant EventHandler
    note over Client,EventHandler: Aggregate Processing Workflow
    Client->>+AppSync: Send multiple events to channel
    AppSync->>+Lambda: Invoke Lambda with batch of events
    Lambda->>+EventHandler: Process events with aggregate=True
    EventHandler->>EventHandler: Batch of events
    EventHandler->>EventHandler: Process entire batch at once
    EventHandler->>EventHandler: Format response for each event
    EventHandler-->>-Lambda: Return aggregated results
    Lambda-->>-AppSync: Return success responses
    AppSync-->>-Client: Confirm all events processed

Authorization fails for publish¶

sequenceDiagram
    participant Client
    participant AppSync
    participant Lambda
    participant EventHandler
    note over Client,EventHandler: Publish Event Authorization Flow
    Client->>AppSync: Publish message to channel
    AppSync->>Lambda: Invoke Lambda with publish event
    Lambda->>EventHandler: Process publish event
    alt Authorization Failed
        EventHandler->>EventHandler: Authorization check fails
        EventHandler->>Lambda: Raise UnauthorizedException
        Lambda->>AppSync: Return error response
        AppSync--xClient: Message not delivered
        AppSync--xAppSync: No distribution to subscribers
    else Authorization Passed
        EventHandler->>Lambda: Return successful response
        Lambda->>AppSync: Return processed event
        AppSync->>Client: Acknowledge message
        AppSync->>AppSync: Distribute to subscribers
    end

Authorization fails for subscribe¶

sequenceDiagram
    participant Client
    participant AppSync
    participant Lambda
    participant EventHandler
    note over Client,EventHandler: Subscribe Event Authorization Flow
    Client->>AppSync: Request subscription to channel
    AppSync->>Lambda: Invoke Lambda with subscribe event
    Lambda->>EventHandler: Process subscribe event
    alt Authorization Failed
        EventHandler->>EventHandler: Authorization check fails
        EventHandler->>Lambda: Raise UnauthorizedException
        Lambda->>AppSync: Return error response
        AppSync--xClient: Subscription denied (HTTP 403)
    else Authorization Passed
        EventHandler->>Lambda: Return successful response
        Lambda->>AppSync: Return authorization success
        AppSync->>Client: Subscription established
    end

Testing your code¶

You can test your event handlers by passing a mocked or actual AppSync Events Lambda event.

Testing publish events¶

Test Publish eventsPublish event json

Testing subscribe events¶

Test Subscribe with code payload mock