Skip to content

Commit b478675

Browse files
Release Model Changes:
f8ed2e57-186a-46df-ac2f-23123b9f8339 a72709ce-58d5-4a9e-9753-56466a8a95d6
1 parent b51b62b commit b478675

File tree

3 files changed

+108
-8
lines changed

3 files changed

+108
-8
lines changed

gradle.properties

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
model.all.version=1.0.159
1+
model.all.version=1.0.160
22
model.accessanalyzer.version=1.0.4
33
model.account.version=1.0.3
44
model.acm.version=1.0.3
@@ -124,7 +124,7 @@ model.dsql.version=1.0.5
124124
model.dynamodb.version=1.0.8
125125
model.dynamodb-streams.version=1.0.4
126126
model.ebs.version=1.0.2
127-
model.ec2.version=1.0.61
127+
model.ec2.version=1.0.62
128128
model.ec2-instance-connect.version=1.0.2
129129
model.ecr.version=1.0.8
130130
model.ecr-public.version=1.0.2
@@ -153,7 +153,7 @@ model.forecastquery.version=1.0.2
153153
model.frauddetector.version=1.0.2
154154
model.freetier.version=1.0.2
155155
model.fsx.version=1.0.9
156-
model.gamelift.version=1.0.5
156+
model.gamelift.version=1.0.6
157157
model.gameliftstreams.version=1.0.8
158158
model.geo-maps.version=1.0.3
159159
model.geo-places.version=1.0.4

models/ec2/service/2016-11-15/ec2-2016-11-15.json

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81643,6 +81643,42 @@
8164381643
"traits": {
8164481644
"smithy.api#enumValue": "mac-m4max.metal"
8164581645
}
81646+
},
81647+
"g7e_2xlarge": {
81648+
"target": "smithy.api#Unit",
81649+
"traits": {
81650+
"smithy.api#enumValue": "g7e.2xlarge"
81651+
}
81652+
},
81653+
"g7e_4xlarge": {
81654+
"target": "smithy.api#Unit",
81655+
"traits": {
81656+
"smithy.api#enumValue": "g7e.4xlarge"
81657+
}
81658+
},
81659+
"g7e_8xlarge": {
81660+
"target": "smithy.api#Unit",
81661+
"traits": {
81662+
"smithy.api#enumValue": "g7e.8xlarge"
81663+
}
81664+
},
81665+
"g7e_12xlarge": {
81666+
"target": "smithy.api#Unit",
81667+
"traits": {
81668+
"smithy.api#enumValue": "g7e.12xlarge"
81669+
}
81670+
},
81671+
"g7e_24xlarge": {
81672+
"target": "smithy.api#Unit",
81673+
"traits": {
81674+
"smithy.api#enumValue": "g7e.24xlarge"
81675+
}
81676+
},
81677+
"g7e_48xlarge": {
81678+
"target": "smithy.api#Unit",
81679+
"traits": {
81680+
"smithy.api#enumValue": "g7e.48xlarge"
81681+
}
8164681682
}
8164781683
}
8164881684
},

models/gamelift/service/2015-10-01/gamelift-2015-10-01.json

Lines changed: 69 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2783,7 +2783,7 @@
27832783
"TimeoutInSeconds": {
27842784
"target": "com.amazonaws.gamelift#WholeNumber",
27852785
"traits": {
2786-
"smithy.api#documentation": "<p>The maximum time, in seconds, that a new game session placement request remains in the queue. When a request exceeds this time, the game session placement changes to a <code>TIMED_OUT</code> status. If you don't specify a request timeout, the queue uses a default value.</p>"
2786+
"smithy.api#documentation": "<p>The maximum time, in seconds, that a new game session placement request remains in the queue. When a request exceeds this time, the game session placement changes to a <code>TIMED_OUT</code> status. If you don't specify a request timeout, the queue uses a default value.</p>\n <note>\n <p>The minimum value is 10 and the maximum value is 600.</p>\n </note>"
27872787
}
27882788
},
27892789
"PlayerLatencyPolicies": {
@@ -10815,6 +10815,12 @@
1081510815
"traits": {
1081610816
"smithy.api#documentation": "<p>The number and status of game server container groups deployed in a container fleet. </p>"
1081710817
}
10818+
},
10819+
"ManagedCapacityConfiguration": {
10820+
"target": "com.amazonaws.gamelift#ManagedCapacityConfiguration",
10821+
"traits": {
10822+
"smithy.api#documentation": "<p>Configuration settings for managed capacity scaling.</p>"
10823+
}
1081810824
}
1081910825
},
1082010826
"traits": {
@@ -14002,7 +14008,7 @@
1400214008
"TimeoutInSeconds": {
1400314009
"target": "com.amazonaws.gamelift#WholeNumber",
1400414010
"traits": {
14005-
"smithy.api#documentation": "<p>The maximum time, in seconds, that a new game session placement request remains in the queue. When a request exceeds this time, the game session placement changes to a <code>TIMED_OUT</code> status.</p>"
14011+
"smithy.api#documentation": "<p>The maximum time, in seconds, that a new game session placement request remains in the queue. When a request exceeds this time, the game session placement changes to a <code>TIMED_OUT</code> status.</p>\n <note>\n <p>The minimum value is 10 and the maximum value is 600.</p>\n </note>"
1400614012
}
1400714013
},
1400814014
"PlayerLatencyPolicies": {
@@ -16343,6 +16349,26 @@
1634316349
"smithy.api#pattern": "^[a-zA-Z0-9:/\\-\\*]+$"
1634416350
}
1634516351
},
16352+
"com.amazonaws.gamelift#ManagedCapacityConfiguration": {
16353+
"type": "structure",
16354+
"members": {
16355+
"ZeroCapacityStrategy": {
16356+
"target": "com.amazonaws.gamelift#ZeroCapacityStrategy",
16357+
"traits": {
16358+
"smithy.api#documentation": "<p>The strategy Amazon GameLift Servers will use to automatically scale your capacity to and from zero\n instances in response to game session activity. Game session activity refers to any active running sessions\n or game session requests.</p>\n <p>Possible ZeroCapacityStrategy types include:</p>\n <ul>\n <li>\n <p>\n <b>MANUAL</b> -- (default value) Amazon GameLift Servers will not update\n capacity to and from zero on your behalf.</p>\n </li>\n <li>\n <p>\n <b>SCALE_TO_AND_FROM_ZERO</b> -- Amazon GameLift Servers will automatically\n scale out MinSize and DesiredInstances from 0 to 1 in response to a game session request, and will scale\n in MinSize and DesiredInstances to 0 after a period with no game session activity. The duration of\n this scale in period can be configured using ScaleInAfterInactivityMinutes. </p>\n </li>\n </ul>"
16359+
}
16360+
},
16361+
"ScaleInAfterInactivityMinutes": {
16362+
"target": "com.amazonaws.gamelift#ScaleInAfterInactivityMinutes",
16363+
"traits": {
16364+
"smithy.api#documentation": "<p>Length of time, in minutes, that Amazon GameLift Servers will wait before scaling in your MinSize and\n DesiredInstances to 0 after a period with no game session activity. Default: 30 minutes.</p>"
16365+
}
16366+
}
16367+
},
16368+
"traits": {
16369+
"smithy.api#documentation": "<p>Use ManagedCapacityConfiguration with the \"SCALE_TO_AND_FROM_ZERO\" ZeroCapacityStrategy to enable Amazon\n GameLift Servers to fully manage the MinSize value, switching between 0 and 1 based on game session\n activity. This is ideal for eliminating compute costs during periods of no game activity.\n It is particularly beneficial during development when you're away from your desk, iterating on builds\n for extended periods, in production environments serving low-traffic locations, or for games with long,\n predictable downtime windows. By automatically managing capacity between 0 and 1 instances, you avoid paying\n for idle instances while maintaining the ability to serve game sessions when demand arrives. Note that while\n scale-out is triggered immediately upon receiving a game session request, actual game session availability\n depends on your server process startup time, so this approach works best with multi-location Fleets where\n cold-start latency is tolerable. With a \"MANUAL\" ZeroCapacityStrategy Amazon GameLift Servers will not\n modify Fleet MinSize values automatically and will not scale out from zero instances in response to game\n sessions.\n </p>"
16370+
}
16371+
},
1634616372
"com.amazonaws.gamelift#MatchedPlayerSession": {
1634716373
"type": "structure",
1634816374
"members": {
@@ -18200,6 +18226,15 @@
1820018226
"smithy.api#documentation": "<p>The location in Amazon S3 where build or script files are stored for access by\n Amazon GameLift Servers.</p>"
1820118227
}
1820218228
},
18229+
"com.amazonaws.gamelift#ScaleInAfterInactivityMinutes": {
18230+
"type": "integer",
18231+
"traits": {
18232+
"smithy.api#range": {
18233+
"min": 5,
18234+
"max": 1440
18235+
}
18236+
}
18237+
},
1820318238
"com.amazonaws.gamelift#ScalingAdjustmentType": {
1820418239
"type": "enum",
1820518240
"members": {
@@ -20318,7 +20353,7 @@
2031820353
}
2031920354
],
2032020355
"traits": {
20321-
"smithy.api#documentation": "<p>\n <b>This API works with the following fleet types:</b> EC2, Container</p>\n <p>Updates capacity settings for a managed EC2 fleet or managed container fleet. For these\n fleets, you adjust capacity by changing the number of instances in the fleet. Fleet\n capacity determines the number of game sessions and players that the fleet can host\n based on its configuration. For fleets with multiple locations, use this operation to\n manage capacity settings in each location individually.</p>\n <p>Use this operation to set these fleet capacity properties: </p>\n <ul>\n <li>\n <p>Minimum/maximum size: Set hard limits on the number of Amazon EC2 instances allowed. If Amazon GameLift Servers receives a \n request--either through manual update or automatic scaling--it won't change the capacity \n to a value outside of this range.</p>\n </li>\n <li>\n <p>Desired capacity: As an alternative to automatic scaling, manually set the number of Amazon EC2 \n instances to be maintained. \n Before changing a fleet's desired capacity, check the maximum capacity of the\n fleet's Amazon EC2 instance type by calling <a href=\"https://docs.aws.amazon.com/gamelift/latest/apireference/API_DescribeEC2InstanceLimits.html\">DescribeEC2InstanceLimits</a>.</p>\n </li>\n </ul>\n <p>To update capacity for a fleet's home Region, or if the fleet has no remote\n locations, omit the <code>Location</code> parameter. The fleet must be in\n <code>ACTIVE</code> status. </p>\n <p>To update capacity for a fleet's remote location, set the\n <code>Location</code> parameter to the location to update. The location must be in\n <code>ACTIVE</code> status.</p>\n <p>If successful, Amazon GameLift Servers updates the capacity settings and returns the identifiers for\n the updated fleet and/or location. If a requested change to desired capacity exceeds the\n instance type's limit, the <code>LimitExceeded</code> exception occurs. </p>\n <p>Updates often prompt an immediate change in fleet capacity, such as when current\n capacity is different than the new desired capacity or outside the new limits. In this\n scenario, Amazon GameLift Servers automatically initiates steps to add or remove instances in the fleet\n location. You can track a fleet's current capacity by calling <a href=\"https://docs.aws.amazon.com/gamelift/latest/apireference/API_DescribeFleetCapacity.html\">DescribeFleetCapacity</a> or <a href=\"https://docs.aws.amazon.com/gamelift/latest/apireference/API_DescribeFleetLocationCapacity.html\">DescribeFleetLocationCapacity</a>. </p>\n <p>\n <b>Learn more</b>\n </p>\n <p>\n <a href=\"https://docs.aws.amazon.com/gamelift/latest/developerguide/fleets-manage-capacity.html\">Scaling fleet\n capacity</a>\n </p>"
20356+
"smithy.api#documentation": "<p>\n <b>This API works with the following fleet types:</b> EC2, Container</p>\n <p>Updates capacity settings for a managed EC2 fleet or managed container fleet. For these\n fleets, you adjust capacity by changing the number of instances in the fleet. Fleet\n capacity determines the number of game sessions and players that the fleet can host\n based on its configuration. For fleets with multiple locations, use this operation to\n manage capacity settings in each location individually.</p>\n <ul>\n <li>\n <p>Minimum/maximum size: Set hard limits on the number of Amazon EC2 instances allowed. If Amazon GameLift Servers receives a \n request--either through manual update or automatic scaling--it won't change the capacity \n to a value outside of this range.</p>\n </li>\n <li>\n <p>Desired capacity: As an alternative to automatic scaling, manually set the number of Amazon EC2 \n instances to be maintained. \n Before changing a fleet's desired capacity, check the maximum capacity of the\n fleet's Amazon EC2 instance type by calling <a href=\"https://docs.aws.amazon.com/gamelift/latest/apireference/API_DescribeEC2InstanceLimits.html\">DescribeEC2InstanceLimits</a>.</p>\n </li>\n </ul>\n <p>To update capacity for a fleet's home Region, or if the fleet has no remote\n locations, omit the <code>Location</code> parameter. The fleet must be in\n <code>ACTIVE</code> status. </p>\n <p>To update capacity for a fleet's remote location, set the\n <code>Location</code> parameter to the location to update. The location must be in\n <code>ACTIVE</code> status.</p>\n <p>If successful, Amazon GameLift Servers updates the capacity settings and returns the identifiers for\n the updated fleet and/or location. If a requested change to desired capacity exceeds the\n instance type's limit, the <code>LimitExceeded</code> exception occurs. </p>\n <p>Updates often prompt an immediate change in fleet capacity, such as when current\n capacity is different than the new desired capacity or outside the new limits. In this\n scenario, Amazon GameLift Servers automatically initiates steps to add or remove instances in the fleet\n location. You can track a fleet's current capacity by calling <a href=\"https://docs.aws.amazon.com/gamelift/latest/apireference/API_DescribeFleetCapacity.html\">DescribeFleetCapacity</a> or <a href=\"https://docs.aws.amazon.com/gamelift/latest/apireference/API_DescribeFleetLocationCapacity.html\">DescribeFleetLocationCapacity</a>.</p>\n <p> Use ManagedCapacityConfiguration with the \"SCALE_TO_AND_FROM_ZERO\" ZeroCapacityStrategy to enable Amazon\n GameLift Servers to fully manage the MinSize value, switching between 0 and 1 based on game session\n activity. This is ideal for eliminating compute costs during periods of no game activity.\n It is particularly beneficial during development when you're away from your desk, iterating on builds\n for extended periods, in production environments serving low-traffic locations, or for games with long,\n predictable downtime windows. By automatically managing capacity between 0 and 1 instances, you avoid paying\n for idle instances while maintaining the ability to serve game sessions when demand arrives. Note that while\n scale-out is triggered immediately upon receiving a game session request, actual game session availability\n depends on your server process startup time, so this approach works best with multi-location Fleets where\n cold-start latency is tolerable. With a \"MANUAL\" ZeroCapacityStrategy Amazon GameLift Servers will not\n modify Fleet MinSize values automatically and will not scale out from zero instances in response to game\n sessions. This is configurable per-location.</p>\n <p>\n <b>Learn more</b>\n </p>\n <p>\n <a href=\"https://docs.aws.amazon.com/gamelift/latest/developerguide/fleets-manage-capacity.html\">Scaling fleet\n capacity</a>\n </p>"
2032220357
}
2032320358
},
2032420359
"com.amazonaws.gamelift#UpdateFleetCapacityInput": {
@@ -20341,7 +20376,7 @@
2034120376
"MinSize": {
2034220377
"target": "com.amazonaws.gamelift#WholeNumber",
2034320378
"traits": {
20344-
"smithy.api#documentation": "<p>The minimum number of instances that are allowed in the specified fleet location. If\n this parameter is not set, the default is 0.</p>"
20379+
"smithy.api#documentation": "<p>The minimum number of instances that are allowed in the specified fleet location. If\n this parameter is not set, the default is 0. This parameter cannot be set when using a\n ManagedCapacityConfiguration where ZeroCapacityStrategy has a value of SCALE_TO_AND_FROM_ZERO.</p>"
2034520380
}
2034620381
},
2034720382
"MaxSize": {
@@ -20355,6 +20390,12 @@
2035520390
"traits": {
2035620391
"smithy.api#documentation": "<p>The name of a remote location to update fleet capacity settings for, in the form of an\n Amazon Web Services Region code such as <code>us-west-2</code>.</p>"
2035720392
}
20393+
},
20394+
"ManagedCapacityConfiguration": {
20395+
"target": "com.amazonaws.gamelift#ManagedCapacityConfiguration",
20396+
"traits": {
20397+
"smithy.api#documentation": "<p>Configuration for Amazon GameLift Servers-managed capacity scaling options.</p>"
20398+
}
2035820399
}
2035920400
},
2036020401
"traits": {
@@ -20381,6 +20422,12 @@
2038120422
"traits": {
2038220423
"smithy.api#documentation": "<p>The remote location being updated, expressed as an Amazon Web Services Region code, such as\n <code>us-west-2</code>.</p>"
2038320424
}
20425+
},
20426+
"ManagedCapacityConfiguration": {
20427+
"target": "com.amazonaws.gamelift#ManagedCapacityConfiguration",
20428+
"traits": {
20429+
"smithy.api#documentation": "<p>Configuration for Amazon GameLift Servers-managed capacity scaling options.</p>"
20430+
}
2038420431
}
2038520432
},
2038620433
"traits": {
@@ -20767,7 +20814,7 @@
2076720814
"TimeoutInSeconds": {
2076820815
"target": "com.amazonaws.gamelift#WholeNumber",
2076920816
"traits": {
20770-
"smithy.api#documentation": "<p>The maximum time, in seconds, that a new game session placement request remains in the queue. When a request exceeds this time, the game session placement changes to a <code>TIMED_OUT</code> status.</p>"
20817+
"smithy.api#documentation": "<p>The maximum time, in seconds, that a new game session placement request remains in the queue. When a request exceeds this time, the game session placement changes to a <code>TIMED_OUT</code> status.</p>\n <note>\n <p>The minimum value is 10 and the maximum value is 600.</p>\n </note>"
2077120818
}
2077220819
},
2077320820
"PlayerLatencyPolicies": {
@@ -21322,6 +21369,23 @@
2132221369
}
2132321370
}
2132421371
},
21372+
"com.amazonaws.gamelift#ZeroCapacityStrategy": {
21373+
"type": "enum",
21374+
"members": {
21375+
"MANUAL": {
21376+
"target": "smithy.api#Unit",
21377+
"traits": {
21378+
"smithy.api#enumValue": "MANUAL"
21379+
}
21380+
},
21381+
"SCALE_TO_AND_FROM_ZERO": {
21382+
"target": "smithy.api#Unit",
21383+
"traits": {
21384+
"smithy.api#enumValue": "SCALE_TO_AND_FROM_ZERO"
21385+
}
21386+
}
21387+
}
21388+
},
2132521389
"com.amazonaws.gamelift#ZipBlob": {
2132621390
"type": "blob",
2132721391
"traits": {

0 commit comments

Comments
 (0)