create_container_fleet
¶
create_container_fleet(
*,
config_overrides: Optional[GameLiftClientConfig] = None,
fleet_role_arn: Optional[IamRoleArn] = None,
description: Optional[NonZeroAndMaxString] = None,
game_server_container_group_definition_name: Optional[
ContainerGroupDefinitionNameOrArn
] = None,
per_instance_container_group_definition_name: Optional[
ContainerGroupDefinitionNameOrArn
] = None,
instance_connection_port_range: Optional[ConnectionPortRange] = None,
instance_inbound_permissions: Optional[IpPermissionsList] = None,
game_server_container_groups_per_instance: Optional[
GameServerContainerGroupsPerInstance
] = None,
instance_type: Optional[NonZeroAndMaxString] = None,
billing_type: Optional[ContainerFleetBillingType] = None,
locations: Optional[LocationConfigurationList] = None,
metric_groups: Optional[MetricGroupList] = None,
new_game_session_protection_policy: Optional[ProtectionPolicy] = None,
game_session_creation_limit_policy: Optional[GameSessionCreationLimitPolicy] = None,
log_configuration: Optional[LogConfiguration] = None,
tags: Optional[TagList] = None,
player_gateway_mode: Optional[PlayerGatewayMode] = None,
) -> CreateContainerFleetOutput
This API works with the following fleet types: Container
Creates a managed fleet of Amazon Elastic Compute Cloud (Amazon EC2) instances to host your containerized game servers. Use this operation to define how to deploy a container architecture onto each fleet instance and configure fleet settings. You can create a container fleet in any Amazon Web Services Regions that Amazon GameLift Servers supports for multi-location fleets. A container fleet can be deployed to a single location or multiple locations. Container fleets are deployed with Amazon Linux 2023 as the instance operating system.
Define the fleet's container architecture using container group definitions. Each fleet can have one of the following container group types:
-
The game server container group runs your game server build and dependent software. Amazon GameLift Servers deploys one or more replicas of this container group to each fleet instance. The number of replicas depends on the computing capabilities of the fleet instance in use.
-
An optional per-instance container group might be used to run other software that only needs to run once per instance, such as background services, logging, or test processes. One per-instance container group is deployed to each fleet instance.
Each container group can include the definition for one or more containers. A container definition specifies a container image that is stored in an Amazon Elastic Container Registry (Amazon ECR) public or private repository.
Request options
Use this operation to make the following types of requests. Most fleet settings have default values, so you can create a working fleet with a minimal configuration and default values, which you can customize later.
-
Create a fleet with no container groups. You can configure a container fleet and then add container group definitions later. In this scenario, no fleet instances are deployed, and the fleet can't host game sessions until you add a game server container group definition. Provide the following required parameter values:
-
FleetRoleArn
-
-
Create a fleet with a game server container group. Provide the following required parameter values:
-
FleetRoleArn -
GameServerContainerGroupDefinitionName
-
-
Create a fleet with a game server container group and a per-instance container group. Provide the following required parameter values:
-
FleetRoleArn -
GameServerContainerGroupDefinitionName -
PerInstanceContainerGroupDefinitionName
-
Results
If successful, this operation creates a new container fleet resource, places it in PENDING status, and initiates the fleet creation workflow. For fleets with container groups, this workflow starts a fleet deployment and transitions the status to ACTIVE. Fleets without a container group are placed in CREATED status.
You can update most of the properties of a fleet, including container group definitions, and deploy the update across all fleet instances. Use UpdateContainerFleet to deploy a new game server version update across the container fleet.
A managed fleet's runtime environment depends on the Amazon Machine Image (AMI) version it uses. When a new fleet is created, Amazon GameLift Servers assigns the latest available AMI version to the fleet, and all compute instances in that fleet are deployed with that version. To update the AMI version, you must create a new fleet. As a best practice, we recommend replacing your managed fleets every 30 days to maintain a secure and up-to-date runtime environment for your hosted game servers. For guidance, see Security best practices for Amazon GameLift Servers.
Parameters:
-
fleet_role_arn(Optional[IamRoleArn], default:None) –The unique identifier for an Identity and Access Management (IAM) role with permissions to run your containers on resources that are managed by Amazon GameLift Servers. Use an IAM service role with the
GameLiftContainerFleetPolicymanaged policy attached. For more information, see Set up an IAM service role. You can't change this fleet property after the fleet is created.IAM role ARN values use the following pattern:
arn:aws:iam::[Amazon Web Services account]:role/[role name]. -
description(Optional[NonZeroAndMaxString], default:None) –A meaningful description of the container fleet.
-
game_server_container_group_definition_name(Optional[ContainerGroupDefinitionNameOrArn], default:None) –A container group definition resource that describes how to deploy containers with your game server build and support software onto each fleet instance. You can specify the container group definition's name to use the latest version. Alternatively, provide an ARN value with a specific version number.
Create a container group definition by calling CreateContainerGroupDefinition. This operation creates a ContainerGroupDefinition resource.
-
per_instance_container_group_definition_name(Optional[ContainerGroupDefinitionNameOrArn], default:None) –The name of a container group definition resource that describes a set of auxiliary software. A fleet instance has one process for executables in this container group. A per-instance container group is optional. You can update the fleet to add or remove a per-instance container group at any time. You can specify the container group definition's name to use the latest version. Alternatively, provide an ARN value with a specific version number.
Create a container group definition by calling https://docs.aws.amazon.com/gamelift/latest/apireference/API_CreateContainerGroupDefinition.html. This operation creates a https://docs.aws.amazon.com/gamelift/latest/apireference/API_ContainerGroupDefinition.html resource.
-
instance_connection_port_range(Optional[ConnectionPortRange], default:None) –The set of port numbers to open on each fleet instance. A fleet's connection ports map to container ports that are configured in the fleet's container group definitions.
By default, Amazon GameLift Servers calculates an optimal port range based on your fleet configuration. To use the calculated range, don't set this parameter. The values are:
-
Port range: 4192 to a number calculated based on your fleet configuration. Amazon GameLift Servers uses the following formula:
4192 + [# of game server container groups per fleet instance] * [# of container ports in the game server container group definition] + [# of container ports in the per instance container group definition]
You can also choose to manually set this parameter. When manually setting this parameter, you must use port numbers that match the fleet's inbound permissions port range.
If you set values manually, Amazon GameLift Servers no longer calculates a port range for you, even if you later remove the manual settings.
The port range must not overlap with the Amazon GameLift Servers reserved port range
4092-4191. This range is reserved for internal Amazon GameLift Servers services. -
-
instance_inbound_permissions(Optional[IpPermissionsList], default:None) –The IP address ranges and port settings that allow inbound traffic to access game server processes and other processes on this fleet. As a best practice, when remotely accessing a fleet instance, we recommend opening ports only when you need them and closing them when you're finished.
By default, Amazon GameLift Servers calculates an optimal port range based on your fleet configuration. To use the calculated range, don't set this parameter. The values are:
-
Protocol: UDP
-
Port range: 4192 to a number calculated based on your fleet configuration. Amazon GameLift Servers uses the following formula:
4192 + [# of game server container groups per fleet instance] * [# of container ports in the game server container group definition] + [# of container ports in the per instance container group definition]
You can also choose to manually set this parameter. When manually setting this parameter, you must use port numbers that match the fleet's connection port range.
If you set values manually, Amazon GameLift Servers no longer calculates a port range for you, even if you later remove the manual settings.
The port range must not overlap with the Amazon GameLift Servers reserved port range
4092-4191. This range is reserved for internal Amazon GameLift Servers services. -
-
game_server_container_groups_per_instance(Optional[GameServerContainerGroupsPerInstance], default:None) –The number of times to replicate the game server container group on each fleet instance.
By default, Amazon GameLift Servers calculates the maximum number of game server container groups that can fit on each instance. This calculation is based on the CPU and memory resources of the fleet's instance type. To use the calculated maximum, don't set this parameter. If you set this number manually, Amazon GameLift Servers uses your value as long as it's less than the calculated maximum.
-
instance_type(Optional[NonZeroAndMaxString], default:None) –The Amazon EC2 instance type to use for all instances in the fleet. For multi-location fleets, the instance type must be available in the home region and all remote locations. Instance type determines the computing resources and processing power that's available to host your game servers. This includes CPU, memory, storage, and networking capacity.
By default, Amazon GameLift Servers uses the
c5.largeinstance type. If this instance type does not have sufficient resources for your container groups, you can choose a different instance type that better fits your needs. See Amazon Elastic Compute Cloud Instance Types for detailed descriptions of Amazon EC2 instance types.You can't update this fleet property later.
-
billing_type(Optional[ContainerFleetBillingType], default:None) –Indicates whether to use On-Demand or Spot instances for this fleet. Learn more about when to use On-Demand versus Spot Instances. This fleet property can't be changed after the fleet is created.
By default, this property is set to
ON_DEMAND.You can't update this fleet property later.
-
locations(Optional[LocationConfigurationList], default:None) –A set of locations to deploy container fleet instances to. You can add any Amazon Web Services Region or Local Zone that's supported by Amazon GameLift Servers. Provide a list of one or more Amazon Web Services Region codes, such as
us-west-2, or Local Zone names. Also include the fleet's home Region, which is the Amazon Web Services Region where the fleet is created. For a list of supported Regions and Local Zones, see Amazon GameLift Servers service locations for managed hosting. -
metric_groups(Optional[MetricGroupList], default:None) –The name of an Amazon Web Services CloudWatch metric group to add this fleet to. You can use a metric group to aggregate metrics for multiple fleets. You can specify an existing metric group name or use a new name to create a new metric group. Each fleet can have only one metric group, but you can change this value at any time.
-
new_game_session_protection_policy(Optional[ProtectionPolicy], default:None) –Determines whether Amazon GameLift Servers can shut down game sessions on the fleet that are actively running and hosting players. Amazon GameLift Servers might prompt an instance shutdown when scaling down fleet capacity or when retiring unhealthy instances. You can also set game session protection for individual game sessions using UpdateGameSession.
-
NoProtection -- Game sessions can be shut down during active gameplay.
-
FullProtection -- Game sessions in
ACTIVEstatus can't be shut down.
By default, this property is set to
NoProtection. -
-
game_session_creation_limit_policy(Optional[GameSessionCreationLimitPolicy], default:None) –A policy that limits the number of game sessions that each individual player can create on instances in this fleet. The limit applies for a specified span of time.
-
log_configuration(Optional[LogConfiguration], default:None) –A method for collecting container logs for the fleet. Amazon GameLift Servers saves all standard output for each container in logs, including game session logs. You can select from the following methods:
-
CLOUDWATCH-- Send logs to an Amazon CloudWatch log group that you define. Each container emits a log stream, which is organized in the log group. -
S3-- Store logs in an Amazon S3 bucket that you define. -
NONE-- Don't collect container logs.
By default, this property is set to
CLOUDWATCH.Amazon GameLift Servers requires permissions to send logs to other Amazon Web Services services in your account. These permissions are included in the IAM fleet role for this container fleet (see
FleetRoleArn). -
-
tags(Optional[TagList], default:None) –A list of labels to assign to the new fleet resource. Tags are developer-defined key-value pairs. Tagging Amazon Web Services resources is useful for resource management, access management and cost allocation. For more information, see Tagging Amazon Web Services Resources in the Amazon Web Services General Reference.
-
player_gateway_mode(Optional[PlayerGatewayMode], default:None) –Configures player gateway for your fleet. Player gateway provides benefits such as DDoS protection by rate limiting and validating traffic before it reaches game servers, hiding game server IP addresses from players, and providing updated endpoints when relay endpoints become unhealthy.
How it works: When enabled, game clients connect to relay endpoints instead of to your game servers. Player gateway validates player gateway tokens and routes traffic to the appropriate game server. Your game backend calls GetPlayerConnectionDetails to retrieve relay endpoints and player gateway tokens for your game clients. To learn more about this topic, see DDoS protection with Amazon GameLift Servers player gateway.
Possible values include:
-
DISABLED(default) -- Game clients connect to the game server endpoint. Use this when you do not intend to integrate your game with player gateway. -
ENABLED-- Player gateway is available in fleet locations where it is supported. Your game backend can call GetPlayerConnectionDetails to obtain a player gateway token and endpoints for game clients. -
REQUIRED-- Player gateway is available in fleet locations where it is supported, and the fleet can only use locations that support this feature. Attempting to add a remote location to your fleet which does not support player gateway will result in anInvalidRequestException.
-
Raises:
-
ConflictException–The requested operation would cause a conflict with the current state of a service resource associated with the request. Resolve the conflict before retrying this request.
-
InternalServiceException–The service encountered an unrecoverable internal failure while processing the request. Clients can retry such requests immediately or after a waiting period.
-
InvalidRequestException–One or more parameter values in the request are invalid. Correct the invalid parameter values before retrying.
-
LimitExceededException–The requested operation would cause the resource to exceed the allowed service limit. Resolve the issue before retrying.
-
TaggingFailedException–The requested tagging operation did not succeed. This may be due to invalid tag format or the maximum tag limit may have been exceeded. Resolve the issue before retrying.
-
UnauthorizedException–The client failed authentication. Clients should not retry such requests.
-
UnsupportedRegionException–The requested operation is not supported in the Region specified.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_gamelift/_services/game_lift.py
859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 | |