Downloading logs from GameLift container fleet

Yes, it is possible to retrieve logs for a specific game session in a container fleet, but the process differs from traditional GameLift fleets.

For container fleets, logs are automatically captured and stored either in Amazon CloudWatch Logs or Amazon S3, depending on your fleet's log configuration. However, the GetGameSessionLogUrl API operation is not supported for container fleets, which explains the error you encountered.

To retrieve logs for a specific game session in a container fleet:

1. If using CloudWatch Logs:

   • Each container emits its own log stream within the specified CloudWatch log group.
   • The log streams are organized by fleet ID and container.
   • You can use CloudWatch features to search and analyze log data.
   • Look for log entries that correspond to your game session ID within these streams.

2. If using Amazon S3:

   • Logs are stored in the specified S3 bucket in your fleet's home AWS region.
   • You can view, share, or download the content as needed.
   • You may need to search through the logs to find entries related to your specific game session ID.

While the logs may have random-seeming IDs as filenames, the content of the logs should contain information about the game session. You'll need to implement your own method to search and filter these logs based on the game session ID you're interested in.

To make this process easier, consider implementing a logging strategy in your game server code that clearly identifies each game session. For example, you could include the game session ID in your log messages, making it easier to filter and find relevant logs later.

Remember that you can modify a container fleet's logging configuration at any time, but this will require a fleet update deployment.

Sources
How containers work in Amazon GameLift Servers - Amazon GameLift Servers
Faster multiplayer hosting with containers on Amazon GameLift Servers | AWS for Games Blog