Skip to main content

Events & SQS Integration

The Tournament Platform provides real-time tournament event notifications to keep your casino system synchronized with tournament events. Events are delivered via AWS SQS transport, configured at the infrastructure level rather than through API endpoints.

Event Overview

SQS Event Delivery Architecture

SQS Transport Features

  • Reliable Delivery: AWS SQS guarantees with configurable retry policies
  • Event Ordering: FIFO queues ensure sequential delivery per tournament
  • Dead Letter Queues: Automatic handling of failed message processing
  • Scalable Processing: Handle high-volume event streams efficiently
  • Infrastructure-level Configuration: No API management required

SQS Configuration

SQS transport is configured at the infrastructure level rather than through API endpoints. Contact [email protected] for queue setup and configuration.

Queue Setup Requirements

Tournament Event Queue:
  • Queue Type: FIFO (First-In-First-Out) for ordered event processing
  • Message Retention: 14 days (AWS SQS maximum)
  • Visibility Timeout: 30 seconds (configurable based on processing needs)
  • Dead Letter Queue: Configured for failed message handling
  • Content-Based Deduplication: Enabled for automatic duplicate prevention
Permissions Required:
  • sqs:ReceiveMessage - Consume tournament events
  • sqs:DeleteMessage - Acknowledge processed events
  • sqs:GetQueueAttributes - Monitor queue health

Event Types

Tournament Lifecycle Events

Tournament Started

Sent when a tournament begins with actual players:

Tournament Completed

Sent when a tournament finishes with final results:

Tournament Cancelled

Sent when a tournament is cancelled before completion:

Player Events

Player Registered

Sent when a player successfully registers for a tournament:

Player Eliminated

Sent when a player is eliminated from the tournament:

Player Rebought

Sent when a player purchases additional tournament entries:

Game Events

Round Started

Sent when a new tournament round begins:

Round Completed

Sent when a tournament round finishes:

SQS Event Processing

SQS Consumer Implementation

Webhook Testing

Test Webhook Endpoint

Response:

Webhook Delivery Logs

Response:

Error Handling & Reliability

Retry Strategy

The Tournament Platform implements automatic retry with exponential backoff:

Error Response Handling

Monitoring Webhook Health

Security Best Practices

Webhook Security

Signature Verification

Always verify HMAC-SHA256 signatures to ensure webhooks are from Tournament Platform

HTTPS Only

Only accept webhooks over encrypted HTTPS connections

IP Allowlisting

Restrict webhook endpoints to Tournament Platform IP addresses

Secret Rotation

Regularly rotate webhook secret keys and update configurations

Idempotency Handling

Next Steps

Testing & Debugging

Tools and techniques for testing your tournament integration implementation.

Database Schema

Explore the database schema supporting the tournament platform architecture.