Amazon GameLift FlexMatch

aws Matching engineaws-gamelift-flexmatch

Rule-set driven matchmaking service that forms balanced teams from a pool of player tickets.

Provider: aws
Kind: Matching engine
Category: Compute
Official docs: https://docs.aws.amazon.com/gamelift/latest/apireference/API_CreateMatchmakingConfiguration.html

Properties · 3 set by this component

property	type	values	required	kind default	this component
acceptanceRequired · component property	boolean	—	no	—	inherited
algorithm	enum	price-time \| pro-rata	no	price-time	inherited
backfillMode · component property	enum	automatic \| manual	no	—	inherited
deterministic	boolean	—	no	true	▸ false
failover	enum	none \| manual \| automatic	no	none	inherited
flexMatchMode · component property	enum	standalone \| with-queue	no	—	inherited
managed	boolean	—	no	false	▸ true
maxAcceptanceTimeoutSeconds · component property	integer	—	no	600	inherited
maxRequestTimeoutSeconds · component property	integer	—	no	43200	inherited
role	enum	primary \| standby	no	primary	inherited
singleThreaded	boolean	—	no	true	▸ false

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Stateful engine pinned to a single zoneerror

stateful-engine-pinned-to-single-zone

A matching engine, coordination service or event store living in exactly one availability zone, with no failover and no replication, is lost with that zone. Everything that depends on it stops with it.

— all of these hold:
— the node sits inside exactly 1 availability-zone group
— any of these hold:
— the node's `failover` is "none"
— the node's `replicated` is false
— the node's `replication` is "none"

Stateful node without zone redundancyerror

stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

— all of these hold:
— the node's `stateless` is false
— the node sits inside exactly 1 availability-zone group
— this does not hold:
— the node sits inside at least one cell group

Use it in a design

nodes:
  - { id: "gamelift-flexmatch", component: "aws-gamelift-flexmatch" }

Other Matching engine products · 2

Generic matching enginematching-enginematching-engine Order-book matcherorder-book-matchermatching-engine

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Amazon GameLift FlexMatch: rule-set driven matchmaker that forms teams from a ticket pool and
3# either returns the match or starts a game session through a game session queue. Matches are formed
4# by rule sets rather than a price-time order book, so the kind's order-book defaults are overridden.
5# The CreateMatchmakingConfiguration API reference makes AcceptanceRequired and
6# RequestTimeoutSeconds (max 43200) required with no default, caps AcceptanceTimeoutSeconds at 600,
7# and defines FlexMatchMode STANDALONE or WITH_QUEUE and BackfillMode AUTOMATIC or MANUAL.
8schemaVersion: "1"
9type: "component"
10id: "aws-gamelift-flexmatch"
11kind: "matching-engine"
12provider: "aws"
13docs: "https://docs.aws.amazon.com/gamelift/latest/apireference/API_CreateMatchmakingConfiguration.html"
14defaults:
15  managed: true
16  singleThreaded: false
17  deterministic: false
18properties:
19  flexMatchMode:
20    type: "enum"
21    values: ["standalone", "with-queue"]
22  backfillMode:
23    type: "enum"
24    values: ["automatic", "manual"]
25  acceptanceRequired:
26    type: "boolean"
27  maxRequestTimeoutSeconds:
28    type: "integer"
29    default: 43200
30  maxAcceptanceTimeoutSeconds:
31    type: "integer"
32    default: 600

The same page as markdown, for an agent: /catalogue/components/aws-gamelift-flexmatch.md