Set up an AWS user account
Tip
Use these topics to get help with these tasks:
Get a new AWS account for use with Amazon GameLift Servers.
Create a user or group with permissions to work with Amazon GameLift Servers resources.
Set up security credentials (you need these to use the AWS CLI tools and the Amazon GameLift Servers plugins for Unreal and Unity)
As with all AWS services, you need an AWS account to use the Amazon GameLift Servers service and tools. An AWS account serves two primary functions: (1) it gives you a container for all the AWS resources that you create with the account; and (2) it lets you manage security for your AWS resources, including setting up user authentication and controlling user access permissions. There's no cost for creating an AWS account.
Explore Amazon GameLift Servers with or without an AWS account
You don't need an AWS account to:
Discover AWS tools for building, running, and growing game experiences at AWS for Games
. Read the Blog and browse the Solutions for Games library . Learn more about Amazon GameLift Servers in the product overview, FAQs, and resources
. Ask AWS to find answers to your product questions. (Try this one: "Looking for low-cost options to host my multiplayer game".) For a deeper dive, find out what makes Amazon GameLift Servers work in the technical documentation, including developer guides for hosting and matchmaking, and the service API reference guide.
Check out information on Amazon GameLift Servers pricing
and cost optimization techniques. Try the Pricing Calculator to see how hosting costs are calculated based on peak concurrent player usage (CCU). -
Get downloads and see code repositories for Amazon GameLift Servers SDKs, plugins, and toolkits. See Amazon GameLift Servers Getting started
. (You need an AWS account to use them.)
You do need an AWS account to:
-
Follow onboarding workflows with the Amazon GameLift Servers plugins for Unreal and Unity, or use the game server wrapper.
-
Create and manage AWS resources using the AWS Management Console.
-
Create and manage AWS resources using the AWS Command Line Interface.
Use Amazon Q with the In the Amazon GameLift Servers technical documentation to find answers, guidance, and recommendations.
Topics
Sign up for an AWS account
To get started with AWS, you need an AWS account. For information about creating an AWS account, see Getting started with an AWS account in the AWS Account Management Reference Guide.
Set user permissions for Amazon GameLift Servers
Create additional users or extend access permissions to existing users as needed for your Amazon GameLift Servers resources. As a best practice ( Security best practices in IAM), apply least-privilege permissions for all users. For guidance on permissions syntax, see IAM permission examples for Amazon GameLift Servers.
Use following instructions to set user permissions based on how you manage the users in your AWS account.
To provide access, add permissions to your users, groups, or roles:
-
Users and groups in AWS IAM Identity Center:
Create a permission set. Follow the instructions in Create a permission set in the AWS IAM Identity Center User Guide.
-
Users managed in IAM through an identity provider:
Create a role for identity federation. Follow the instructions in Create a role for a third-party identity provider (federation) in the IAM User Guide.
-
IAM users:
-
Create a role that your user can assume. Follow the instructions in Create a role for an IAM user in the IAM User Guide.
-
(Not recommended) Attach a policy directly to a user or add a user to a user group. Follow the instructions in Adding permissions to a user (console) in the IAM User Guide.
-
When working with IAM users, as a best practice always attach permissions to roles or user groups, not individual users.
Set up programmatic access for users
Users need programmatic access if they want to interact with AWS outside of the AWS Management Console. The way to grant programmatic access depends on the type of user that's accessing AWS.
To grant users programmatic access, choose one of the following options.
| Which user needs programmatic access? | To | By |
|---|---|---|
| IAM | (Recommended) Use console credentials as temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. |
Following the instructions for the interface that you want to use.
|
|
Workforce identity (Users managed in IAM Identity Center) |
Use temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. |
Following the instructions for the interface that you want to use.
|
| IAM | Use temporary credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. | Following the instructions in Using temporary credentials with AWS resources in the IAM User Guide. |
| IAM | (Not recommended) Use long-term credentials to sign programmatic requests to the AWS CLI, AWS SDKs, or AWS APIs. |
Following the instructions for the interface that you want to use.
|
If you use access keys, see Best practices for managing AWS access keys.
Set up programmatic access for your game
Most games use backend services to communicate with Amazon GameLift Servers using the AWS SDKs. Use a backend service (acting for a game client) to request game sessions, place players into games, and other tasks. These services need programmatic access and security credentials to authenticate calls to the service API for Amazon GameLift Servers.
For Amazon GameLift Servers, you manage this access by creating a player user in AWS Identity and Access Management (IAM). Manage player user permissions through one of the following options:
-
Create an IAM role with player user permissions and allow the player user to assume the role when needed. The backend service must include code to assume this role before making requests to Amazon GameLift Servers. In accordance with security best practices, roles provide limited, temporary access. You can use roles for workloads running on AWS resources (IAM roles) or outside of AWS (IAM Roles Anywhere).
-
Create an IAM user group with player user permissions and add your player user to the group. This option gives your player user long-term credentials, which the backend service must store and use when communicating with Amazon GameLift Servers.
For permissions policy syntax, see Player user permission examples.
For more information on managing permissions for use by a workload, see IAM Identities: Temporary credentials in IAM.
