GameLift#
Client#
- class GameLift.Client#
A low-level client representing Amazon GameLift
Amazon GameLift provides solutions for hosting session-based multiplayer game servers in the cloud, including tools for deploying, operating, and scaling game servers. Built on Amazon Web Services global computing infrastructure, GameLift helps you deliver high-performance, high-reliability, low-cost game servers while dynamically scaling your resource usage to meet player demand.
About Amazon GameLift solutions
Get more information on these Amazon GameLift solutions in the Amazon GameLift Developer Guide.
Amazon GameLift managed hosting – Amazon GameLift offers a fully managed service to set up and maintain computing machines for hosting, manage game session and player session life cycle, and handle security, storage, and performance tracking. You can use automatic scaling tools to balance player demand and hosting costs, configure your game session management to minimize player latency, and add FlexMatch for matchmaking.
Managed hosting with Realtime Servers – With Amazon GameLift Realtime Servers, you can quickly configure and set up ready-to-go game servers for your game. Realtime Servers provides a game server framework with core Amazon GameLift infrastructure already built in. Then use the full range of Amazon GameLift managed hosting features, including FlexMatch, for your game.
Amazon GameLift FleetIQ – Use Amazon GameLift FleetIQ as a standalone service while hosting your games using EC2 instances and Auto Scaling groups. Amazon GameLift FleetIQ provides optimizations for game hosting, including boosting the viability of low-cost Spot Instances gaming. For a complete solution, pair the Amazon GameLift FleetIQ and FlexMatch standalone services.
Amazon GameLift FlexMatch – Add matchmaking to your game hosting solution. FlexMatch is a customizable matchmaking service for multiplayer games. Use FlexMatch as integrated with Amazon GameLift managed hosting or incorporate FlexMatch as a standalone service into your own hosting solution.
About this API Reference
This reference guide describes the low-level service API for Amazon GameLift. With each topic in this guide, you can find links to language-specific SDK guides and the Amazon Web Services CLI reference. Useful links:
import boto3 client = boto3.client('gamelift')
These are the available methods:
- accept_match
- can_paginate
- claim_game_server
- close
- create_alias
- create_build
- create_fleet
- create_fleet_locations
- create_game_server_group
- create_game_session
- create_game_session_queue
- create_location
- create_matchmaking_configuration
- create_matchmaking_rule_set
- create_player_session
- create_player_sessions
- create_script
- create_vpc_peering_authorization
- create_vpc_peering_connection
- delete_alias
- delete_build
- delete_fleet
- delete_fleet_locations
- delete_game_server_group
- delete_game_session_queue
- delete_location
- delete_matchmaking_configuration
- delete_matchmaking_rule_set
- delete_scaling_policy
- delete_script
- delete_vpc_peering_authorization
- delete_vpc_peering_connection
- deregister_compute
- deregister_game_server
- describe_alias
- describe_build
- describe_compute
- describe_ec2_instance_limits
- describe_fleet_attributes
- describe_fleet_capacity
- describe_fleet_events
- describe_fleet_location_attributes
- describe_fleet_location_capacity
- describe_fleet_location_utilization
- describe_fleet_port_settings
- describe_fleet_utilization
- describe_game_server
- describe_game_server_group
- describe_game_server_instances
- describe_game_session_details
- describe_game_session_placement
- describe_game_session_queues
- describe_game_sessions
- describe_instances
- describe_matchmaking
- describe_matchmaking_configurations
- describe_matchmaking_rule_sets
- describe_player_sessions
- describe_runtime_configuration
- describe_scaling_policies
- describe_script
- describe_vpc_peering_authorizations
- describe_vpc_peering_connections
- get_compute_access
- get_compute_auth_token
- get_game_session_log_url
- get_instance_access
- get_paginator
- get_waiter
- list_aliases
- list_builds
- list_compute
- list_fleets
- list_game_server_groups
- list_game_servers
- list_locations
- list_scripts
- list_tags_for_resource
- put_scaling_policy
- register_compute
- register_game_server
- request_upload_credentials
- resolve_alias
- resume_game_server_group
- search_game_sessions
- start_fleet_actions
- start_game_session_placement
- start_match_backfill
- start_matchmaking
- stop_fleet_actions
- stop_game_session_placement
- stop_matchmaking
- suspend_game_server_group
- tag_resource
- untag_resource
- update_alias
- update_build
- update_fleet_attributes
- update_fleet_capacity
- update_fleet_port_settings
- update_game_server
- update_game_server_group
- update_game_session
- update_game_session_queue
- update_matchmaking_configuration
- update_runtime_configuration
- update_script
- validate_matchmaking_rule_set
Paginators#
Paginators are available on a client instance via the get_paginator method. For more detailed instructions and examples on the usage of paginators, see the paginators user guide.
The available paginators are:
- DescribeFleetAttributes
- DescribeFleetCapacity
- DescribeFleetEvents
- DescribeFleetUtilization
- DescribeGameServerInstances
- DescribeGameSessionDetails
- DescribeGameSessionQueues
- DescribeGameSessions
- DescribeInstances
- DescribeMatchmakingConfigurations
- DescribeMatchmakingRuleSets
- DescribePlayerSessions
- DescribeScalingPolicies
- ListAliases
- ListBuilds
- ListCompute
- ListFleets
- ListGameServerGroups
- ListGameServers
- ListLocations
- ListScripts
- SearchGameSessions