Instance Attribute Details

#event_code ⇒ String

Type of event being logged. The following events are currently in
use:

General events:

GENERIC_EVENT – An unspecified event has occurred.

^

Fleet creation events:

FLEET_CREATED – A fleet record was successfully created
with a status of NEW. Event messaging includes the fleet ID.

FLEET_STATE_DOWNLOADING – Fleet status changed from NEW
to DOWNLOADING. The compressed build has started downloading
to a fleet instance for installation.

FLEET_BINARY_DOWNLOAD_FAILED – The build failed to
download to the fleet instance.

FLEET_CREATION_EXTRACTING_BUILD – The game server build
was successfully downloaded to an instance, and the build files
are now being extracted from the uploaded build and saved to an
instance. Failure at this stage prevents a fleet from moving to
ACTIVE status. Logs for this stage display a list of the files
that are extracted and saved on the instance. Access the logs by
using the URL in PreSignedLogUrl.

FLEET_CREATION_RUNNING_INSTALLER – The game server build
files were successfully extracted, and the Amazon GameLift is
now running the build's install script (if one is included).
Failure in this stage prevents a fleet from moving to ACTIVE
status. Logs for this stage list the installation steps and
whether or not the install completed successfully. Access the
logs by using the URL in PreSignedLogUrl.

FLEET_CREATION_VALIDATING_RUNTIME_CONFIG – The build
process was successful, and the Amazon GameLift is now verifying
that the game server launch paths, which are specified in the
fleet's run-time configuration, exist. If any listed launch
path exists, Amazon GameLift tries to launch a game server
process and waits for the process to report ready. Failures in
this stage prevent a fleet from moving to ACTIVE status. Logs
for this stage list the launch paths in the run-time
configuration and indicate whether each is found. Access the
logs by using the URL in PreSignedLogUrl.

FLEET_VALIDATION_EXECUTABLE_RUNTIME_FAILURE – Validation
of the run-time configuration failed because the executable
specified in a launch path failed to run on the fleet instance.

FLEET_STATE_ACTIVATING – Fleet status changed from
BUILDING to ACTIVATING.

FLEET_ACTIVATION_FAILED - The fleet failed to successfully
complete one of the steps in the fleet activation process. This
event code indicates that the game build was successfully
downloaded to a fleet instance, built, and validated, but was
not able to start a server process. A possible reason for
failure is that the game server is not reporting "process
ready" to the Amazon GameLift service.

FLEET_STATE_ACTIVE – The fleet's status changed from
ACTIVATING to ACTIVE. The fleet is now ready to host game
sessions.

Other fleet events:

FLEET_SCALING_EVENT – A change was made to the fleet's
capacity settings (desired instances, minimum/maximum scaling
limits). Event messaging includes the new capacity settings.

FLEET_NEW_GAME_SESSION_PROTECTION_POLICY_UPDATED – A
change was made to the fleet's game session protection policy
setting. Event messaging includes both the old and new policy
setting.

#pre_signed_log_url ⇒ String

Location of stored logs with additional detail that is related to
the event. This is useful for debugging issues. The URL is valid for
15 minutes. You can also access fleet creation logs through the
Amazon GameLift console.