Crossplay Integration Kit

AWS Lambda

Complete Lambda SDK nodes and portable backend-function calls

AWS Lambda

AWSIKLambda wraps all 87 active operations in the pinned model; the one SDK-deprecated operation is an explicitly classified omission. The portable backend-function role exposes one gameplay operation: call a configured function name with a JSON object and receive its JSON response. The Blueprint action derives from UBetideAsyncAction, validates the JSON before network I/O, survives garbage collection, and finishes once on the game thread.

Grant clients lambda:InvokeFunction only for an explicit allow-list of gameplay functions. Function creation, configuration, aliases, versions, event sources, layers, concurrency, signing, URLs, and policy nodes are Trusted Backend. Prefer invoking a narrow function over granting a player direct write permissions for sensitive progression or economy data.

Lambda function errors remain successful transport responses with the function-error field available to raw callers; the portable role maps malformed or failed JSON responses to a structured FBetideError.

On this page