UpdateMatchmakingConfiguration
Updates settings for a FlexMatch matchmaking configuration. These changes affect all matches and game sessions that are created after the update. To update settings, specify the configuration name to be updated and provide the new settings.
Learn more
Request Syntax
{
"AcceptanceRequired": boolean
,
"AcceptanceTimeoutSeconds": number
,
"AdditionalPlayerCount": number
,
"BackfillMode": "string
",
"CustomEventData": "string
",
"Description": "string
",
"FlexMatchMode": "string
",
"GameProperties": [
{
"Key": "string
",
"Value": "string
"
}
],
"GameSessionData": "string
",
"GameSessionQueueArns": [ "string
" ],
"Name": "string
",
"NotificationTarget": "string
",
"RequestTimeoutSeconds": number
,
"RuleSetName": "string
"
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
Note
In the following list, the required parameters are described first.
- Name
-
A unique identifier for the matchmaking configuration to update. You can use either the configuration name or ARN value.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 256.
Pattern:
[a-zA-Z0-9-\.]*|^arn:.*:matchmakingconfiguration\/[a-zA-Z0-9-\.]*
Required: Yes
- AcceptanceRequired
-
A flag that indicates whether a match that was created with this configuration must be accepted by the matched players. To require acceptance, set to TRUE. With this option enabled, matchmaking tickets use the status
REQUIRES_ACCEPTANCE
to indicate when a completed potential match is waiting for player acceptance.Type: Boolean
Required: No
- AcceptanceTimeoutSeconds
-
The length of time (in seconds) to wait for players to accept a proposed match, if acceptance is required.
Type: Integer
Valid Range: Minimum value of 1. Maximum value of 600.
Required: No
- AdditionalPlayerCount
-
The number of player slots in a match to keep open for future players. For example, if the configuration's rule set specifies a match for a single 12-person team, and the additional player count is set to 2, only 10 players are selected for the match. This parameter is not used if
FlexMatchMode
is set toSTANDALONE
.Type: Integer
Valid Range: Minimum value of 0.
Required: No
- BackfillMode
-
The method that is used to backfill game sessions created with this matchmaking configuration. Specify MANUAL when your game manages backfill requests manually or does not use the match backfill feature. Specify AUTOMATIC to have GameLift create a match backfill request whenever a game session has one or more open slots. Learn more about manual and automatic backfill in Backfill Existing Games with FlexMatch. Automatic backfill is not available when
FlexMatchMode
is set toSTANDALONE
.Type: String
Valid Values:
AUTOMATIC | MANUAL
Required: No
- CustomEventData
-
Information to add to all events related to the matchmaking configuration.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 256.
Required: No
- Description
-
A description for the matchmaking configuration.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 1024.
Required: No
- FlexMatchMode
-
Indicates whether this matchmaking configuration is being used with Amazon GameLift Servers hosting or as a standalone matchmaking solution.
-
STANDALONE - FlexMatch forms matches and returns match information, including players and team assignments, in a MatchmakingSucceeded event.
-
WITH_QUEUE - FlexMatch forms matches and uses the specified Amazon GameLift Servers queue to start a game session for the match.
Type: String
Valid Values:
STANDALONE | WITH_QUEUE
Required: No
-
- GameProperties
-
A set of key-value pairs that can store custom data in a game session. For example:
{"Key": "difficulty", "Value": "novice"}
. This information is added to the newGameSession
object that is created for a successful match. This parameter is not used ifFlexMatchMode
is set toSTANDALONE
.Type: Array of GameProperty objects
Array Members: Maximum number of 16 items.
Required: No
- GameSessionData
-
A set of custom game session properties, formatted as a single string value. This data is passed to a game server process with a request to start a new game session. For more information, see Start a game session. This information is added to the game session that is created for a successful match. This parameter is not used if
FlexMatchMode
is set toSTANDALONE
.Type: String
Length Constraints: Minimum length of 1. Maximum length of 4096.
Required: No
- GameSessionQueueArns
-
The Amazon Resource Name (ARN) that is assigned to a Amazon GameLift Servers game session queue resource and uniquely identifies it. ARNs are unique across all Regions. Format is
arn:aws:gamelift:<region>::gamesessionqueue/<queue name>
. Queues can be located in any Region. Queues are used to start new Amazon GameLift Servers-hosted game sessions for matches that are created with this matchmaking configuration. IfFlexMatchMode
is set toSTANDALONE
, do not set this parameter.Type: Array of strings
Length Constraints: Minimum length of 1. Maximum length of 512.
Pattern:
[a-zA-Z0-9:/-]+
Required: No
- NotificationTarget
-
An SNS topic ARN that is set up to receive matchmaking notifications. See Setting up notifications for matchmaking for more information.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 300.
Pattern:
[a-zA-Z0-9:_/-]*(.fifo)?
Required: No
- RequestTimeoutSeconds
-
The maximum duration, in seconds, that a matchmaking ticket can remain in process before timing out. Requests that fail due to timing out can be resubmitted as needed.
Type: Integer
Valid Range: Minimum value of 1. Maximum value of 43200.
Required: No
- RuleSetName
-
A unique identifier for the matchmaking rule set to use with this configuration. You can use either the rule set name or ARN value. A matchmaking configuration can only use rule sets that are defined in the same Region.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 256.
Pattern:
[a-zA-Z0-9-\.]*|^arn:.*:matchmakingruleset\/[a-zA-Z0-9-\.]*
Required: No
Response Syntax
{
"Configuration": {
"AcceptanceRequired": boolean,
"AcceptanceTimeoutSeconds": number,
"AdditionalPlayerCount": number,
"BackfillMode": "string",
"ConfigurationArn": "string",
"CreationTime": number,
"CustomEventData": "string",
"Description": "string",
"FlexMatchMode": "string",
"GameProperties": [
{
"Key": "string",
"Value": "string"
}
],
"GameSessionData": "string",
"GameSessionQueueArns": [ "string" ],
"Name": "string",
"NotificationTarget": "string",
"RequestTimeoutSeconds": number,
"RuleSetArn": "string",
"RuleSetName": "string"
}
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- Configuration
-
The updated matchmaking configuration.
Type: MatchmakingConfiguration object
Errors
For information about the errors that are common to all actions, see Common Errors.
- InternalServiceException
-
The service encountered an unrecoverable internal failure while processing the request. Clients can retry such requests immediately or after a waiting period.
HTTP Status Code: 500
- InvalidRequestException
-
One or more parameter values in the request are invalid. Correct the invalid parameter values before retrying.
HTTP Status Code: 400
- NotFoundException
-
The requested resources was not found. The resource was either not created yet or deleted.
HTTP Status Code: 400
- UnsupportedRegionException
-
The requested operation is not supported in the Region specified.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: