class Aws::GameLift::Types::Event

@see docs.aws.amazon.com/goto/WebAPI/gamelift-2015-10-01/Event AWS API Documentation
@return [Integer]
The number of times that this event occurred.
@!attribute [rw] count
@return [String]
Amazon GameLift Servers console.
15 minutes. You can also access fleet creation logs through the
the event. This is useful for debugging issues. The URL is valid for
Location of stored logs with additional detail that is related to
@!attribute [rw] pre_signed_log_url
@return [Time]
‘“1469498468.057”`).
expressed in Unix time as milliseconds (for example
Time stamp indicating when this event occurred. Format is a number
@!attribute [rw] event_time
@return [String]
Additional information related to the event.
@!attribute [rw] message
@return [String]<br>: docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/invalid-peering-configurations.html<br>[1]: docs.aws.amazon.com/gamelift/latest/developerguide/fleets-creating-debug.html#fleets-creating-debug-creation<br><br><br><br>* GENERIC_EVENT – An unspecified event has occurred.
* FLEET_DELETED – A request to delete a fleet was initiated.
Event messaging includes both the old and new policy setting.
was made to the fleet’s game session protection policy setting.
* FLEET_NEW_GAME_SESSION_PROTECTION_POLICY_UPDATED – A change
limits). Event messaging includes the new capacity settings.
capacity settings (desired instances, minimum/maximum scaling
* FLEET_SCALING_EVENT – A change was made to the fleet’s
**Other fleet events:**
^
expected.
see why ‘ActivateGameSession()` took longer to complete than
activate within the expected time. Check your game session log to
* GAME_SESSION_ACTIVATION_TIMEOUT – GameSession failed to
**Game session events:**
termination took longer than expected.
calling `ProcessEnding()`. Check your game session log to see why
not exit cleanly within the time expected (30 seconds) after
* SERVER_PROCESS_PROCESS_EXIT_TIMEOUT – The server process did
longer than expected.
was sent. Check your game session log to see why termination took
exit cleanly within the time expected after `OnProcessTerminate()`
* SERVER_PROCESS_FORCE_TERMINATED – The server process did not
thread became stuck processing a synchronous task for too long.
terminated by GameLift. Check your game session log to see if the
not report a valid health check for too long and was therefore
* SERVER_PROCESS_TERMINATED_UNHEALTHY – The server process did
`ProcessEnding()` was not called.
calling `ProcessEnding()`. Check your game session log to see why
* SERVER_PROCESS_CRASHED – The server process exited without
`ProcessReady()` was not called in time.
after calling `InitSDK()`. Check your game session log to see why
not call `ProcessReady()` within the time expected (5 minutes)
* SERVER_PROCESS_PROCESS_READY_TIMEOUT – The server process did
the Amazon GameLift Servers Agent.
container fleets and Anywhere fleets unless they’re deployed with
not called in time. This event is not emitted for managed
minutes). Check your game session log to see why ‘InitSDK()` was
process did not call `InitSDK()` within the time expected (5
* SERVER_PROCESS_SDK_INITIALIZATION_TIMEOUT – The server
operating system of the Fleet.
configuration. Check that the launch path is correct based on the
script could not be found based on the Fleet runtime
* SERVER_PROCESS_INVALID_PATH – The game server executable or
**Server process events:**
has no active game sessions.
high risk of interruption and is scheduled to be recycled once it
* INSTANCE_RECYCLED – A spot instance was determined to have a
with a two-minute notification.
* INSTANCE_INTERRUPTED – A spot instance was interrupted by EC2
**Spot instance events:**
successfully deleted.
* FLEET_VPC_PEERING_DELETED – A VPC peering connection has been

[https://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/invalid-peering-configurations.html][2]
see
Services account. For more information on VPC peering failures,
resolve this, change the CIDR block for the VPC in your Amazon Web
two VPCs have overlapping CIDR blocks of IPv4 addresses. To
additional detail. A common reason for peering failure is that the
has failed. Event details and status information provide
* FLEET_VPC_PEERING_FAILED – A requested VPC peering connection
fleet and a VPC in your Amazon Web Services account.
been established between the VPC for an Amazon GameLift Servers
* FLEET_VPC_PEERING_SUCCEEDED – A VPC peering connection has
**VPC peering events:**
details.
during fleet creation. Describe the fleet event message for more
* FLEET_INITIALIZATION_FAILED – A generic exception occurred
fleet attributes such as fleet type, instance type, etc.
Try again at a different time or choose a different combination of
able to obtain any instances based on the input fleet attributes.
* FLEET_ACTIVATION_FAILED_NO_INSTANCES – Fleet creation was not
Fleet Creation Issues].
able to start a server process. For more information, see [Debug
downloaded to a fleet instance, built, and validated, but was not
event code indicates that the game build was successfully
complete one of the steps in the fleet activation process. This
* FLEET_ACTIVATION_FAILED – The fleet failed to successfully
end of creation timed out. Try fleet creation again.
* FLEET_VALIDATION_TIMED_OUT – Validation of the fleet at the
in a launch path failed to run on the fleet instance.
the runtime configuration failed because the executable specified
* FLEET_VALIDATION_EXECUTABLE_RUNTIME_FAILURE – Validation of
launch path does not exist on the instance.
runtime configuration failed because the executable specified in a
* FLEET_VALIDATION_LAUNCH_PATH_NOT_FOUND – Validation of the
PreSignedLogUrl.
each is found. Access the logs by using the URL in
launch paths in the runtime configuration and indicate whether
fleet from moving to `ACTIVE` status. Logs for this stage list the
for the process to report ready. Failures in this stage prevent a
GameLift Servers tries to launch a game server process and waits
configuration, exist. If any listed launch path exists, Amazon
server launch paths, which are specified in the fleet’s runtime
was successful, and the GameLift is now verifying that the game
* FLEET_CREATION_VALIDATING_RUNTIME_CONFIG – The build process
validation.
the failure occurred before Amazon GameLift Servers could start
attempting to install the build files. This event indicates that
* FLEET_CREATION_FAILED_INSTALLER – The installed failed while
installation will begin soon.
files were successfully installed and validation of the
* FLEET_CREATION_COMPLETED_INSTALLER – The game server build
in PreSignedLogUrl.
install completed successfully. Access the logs by using the URL
for this stage list the installation steps and whether or not the
in this stage prevents a fleet from moving to ACTIVE status. Logs
running the build’s install script (if one is included). Failure
were successfully extracted, and Amazon GameLift Servers is now
* FLEET_CREATION_RUNNING_INSTALLER – The game server build files
URL in PreSignedLogUrl.
extracted and saved on the instance. Access the logs by using the
status. Logs for this stage display a list of the files that are
Failure at this stage prevents a fleet from moving to ACTIVE
Serversis now extracting the build files from the uploaded build.
successfully downloaded to an instance, and Amazon GameLift
* FLEET_CREATION_EXTRACTING_BUILD – The game server build was
the fleet instance.
* FLEET_BINARY_DOWNLOAD_FAILED – The build failed to download to
**Fleet creation events (ordered by fleet creation activity):**
Describe the fleet event message for more details.
* FLEET_STATE_ERROR – The Fleet’s status changed to ‘ERROR`.
sessions.
`ACTIVATING` to `ACTIVE`. The fleet is now ready to host game
* FLEET_STATE_ACTIVE – The fleet’s status changed from
connectivity with the Amazon GameLift Servers service.
server process on the fleet instance and is testing its
to ‘ACTIVATING`. Amazon GameLift Servers is launching a game
* FLEET_STATE_ACTIVATING – Fleet status changed from `BUILDING`
the build files and is now launching a fleet instance.
to `BUILDING`. Amazon GameLift Servers has successfully verified
* FLEET_STATE_BUILDING – Fleet status changed from `VALIDATING`
files.
successfully installed build and is now validating the build
`DOWNLOADING` to `VALIDATING`. Amazon GameLift Servers has
* FLEET_STATE_VALIDATING – Fleet status changed from
compressed build and running install scripts.
`DOWNLOADING`. Amazon GameLift Servers is downloading the
* FLEET_STATE_DOWNLOADING – Fleet status changed from `NEW` to
status of `NEW`. Event messaging includes the fleet ID.
* FLEET_CREATED – A fleet resource was successfully created with a
**Fleet state transition events:**
The type of event being logged.
@!attribute [rw] event_code
@return [String]
A unique identifier for an event resource, such as a fleet ID.
@!attribute [rw] resource_id
@return [String]
A unique identifier for a fleet event.
@!attribute [rw] event_id
troubleshooting and debugging problems.
codes and messages can provide additional information for
resources (such as a fleet). In addition to tracking activity, event
Log entry describing an event that involves Amazon GameLift Servers