This Guidance demonstrates how you can unlock insights and respond to game player behavior using natural language and generative business intelligence. It is powered by large language models (LLMs) in Amazon Bedrock and enhanced with retrieval augmented generation (RAG) using your custom game data. This Guidance shows you how to execute SQL queries that answer business-related questions and create dashboards for player analysis. As a result, it provides timely player insights, enables quicker business decisions, and reduces the burden on game analytics teams.

Note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

Get Started

Deploy this Guidance

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

  • AWS managed services, such as Amazon ECS, Lambda, SageMaker, and Amazon Bedrock, offload the operational burden of provisioning, scaling, patching, and maintaining the underlying infrastructure. This allows you to focus on building and optimizing your application logic, rather than spending time on undifferentiated heavy lifting tasks. With automatic scaling capabilities, your application can handle varying levels of user traffic without compromising performance or availability.

    Read the Operational Excellence whitepaper 

  • AWS Identity and Access Management (IAM) empower you to create and manage AWS users and groups and control their permissions to perform specific actions on specific resources. By providing minimal IAM privileges to your Amazon ECS and Lambda resources, you can enhance the security of your application and protect your AWS environment.

    Read the Security whitepaper 

  • Managed services, such as Amazon ECS and Lambda, offload the responsibility of managing and scaling the underlying infrastructure, so your application can automatically scale and recover from failures. Additionally, OpenSearch Service helps ensure high availability and resilience for your data, providing reliable access to historical search data and continuity of your text-to-SQL functionality.

    Read the Reliability whitepaper 

  • Lambda functions are designed to be highly scalable and efficient, with AWS automatically provisioning and scaling the compute resources required to run your Lambda functions based on incoming traffic. OpenSearch Service leverages advanced indexing and caching mechanisms to provide fast and efficient search capabilities for your historical question and SQL data, optimizing performance for your text-to-SQL functionality.

    Read the Performance Efficiency whitepaper 

  • By using Lambda, you only pay for the compute time consumed, making it a cost-effective option for event-driven workloads. OpenSearch Service is a managed service, which means you don't have to invest in dedicated resources for managing and maintaining search engine infrastructure. You can scale based on actual usage and requirements to optimize costs.

    Read the Cost Optimization whitepaper 

  • The serverless architecture of Lambda eliminates the need for dedicated servers or infrastructure, reducing energy consumption and associated carbon emissions. OpenSearch Service uses AWS Cloud infrastructure, incorporating practices such as energy-efficient data centers and renewable energy sources to minimize environmental impact.

    Read the Sustainability whitepaper 

Related Content

[Content Type]

[Title]

This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.

Was this page helpful?

 Feedback