Game servers transmit JSON-formatted gameplay events to an Amazon Kinesis stream (called
the telemetry stream) that collects and processes those events. A KCL consumer application (called the
S3Connector) validates, sanitizes, and enriches the events, and archives the events as a batch
telemetry file in Amazon S3. The application also sends a pointer to the location
of the batch telemetry file to a separate Amazon Kinesis stream (called the file stream) that initiates the process of loading the data into Amazon Redshift. A second KCL
consumer application (called the RedshiftConnector) loads batches of events from Amazon S3, deletes duplicate events, and inserts events
into tables in Amazon Redshift. A third application (called the CronConnector) performs routine database tasks and maintenance.

Once the data has been loaded into Amazon Redshift, you can use analytics tools and
services, including Amazon QuickSight, for reporting, ad-hoc queries, and more detailed analysis.

AWS Elastic Beanstalk is used to manage the deployment of the solution’s three applications,
from capacity provisioning, load balancing, auto-scaling to application health monitoring.

Javascript is disabled or is unavailable in your browser.

To use the AWS Documentation, Javascript must be enabled. Please refer to your browser's
Help pages for instructions.