Amazon DynamoDB

AWSIKDynamoDB wraps all 58 operations in the pinned model. Use raw nodes for custom data models; use the portable player-data and leaderboard roles for the standard schema.

Deploy Scripts/awsik/tables/player-data.yaml. The player table uses PlayerId as its partition key and RecordKey as its sort key, with Data JSON and a monotonically increasing Version. SetRecord uses an expected-version condition so concurrent writers fail rather than overwrite silently. Stats are atomic increments stored under stat:<name> record keys. The leaderboard table uses LeaderboardId as its partition key and a sortable ScoreKey; returned records include player id, score, rank, and metadata JSON.

Configure the table names in Project Settings > Betide > Crossplay > AWS DynamoDB. The player-data table is required; the leaderboard table is optional and only the leaderboard nodes fail, naming the setting, when it is empty. Player credentials should be restricted to their own partition; leaderboard reads may target explicitly public partitions. Table creation, backup, restore, policy, import/export, replica, and control-plane operations are Trusted Backend.

JSON remains opaque to the adapter. Validate game-specific schemas at the backend boundary and do not store secrets or unbounded user input in records.