This Guidance shows how Hospitality companies can leverage artificial intelligence and event-driven services to automatically trigger check-in and registration activities, providing a more seamless experience for for travelers/guests.
Architecture Diagram
[Architecture diagram description]
Step 1
Ingest real-time customer activity either from central and on-premises systems as application events with Amazon EventBridge or directly from software as a service (SaaS) applications with Amazon AppFlow.
Step 2
Process customer activity and detect the guest location and journey stage (for example, checking in) with AWS Step Functions.
Step 3
Infer the next best action by invoking AWS Lambda and Amazon SageMaker trained machine learning (ML) model.
Step 4
Amazon DynamoDB tables store customer check-in info, location, and recommended next best action, then triggers guest notifications with Amazon DynamoDB Streams.
Step 5
Use Amazon Pinpoint to notify guests about check in, room readiness, and other events over channels like email, SMS, push, or in-app messaging.
Step 6
The hotel’s mobile or web app or on-property guest service apps send requests through an Amazon API Gateway endpoint.
Step 1
Ingest real-time customer activity either from central and on-premises systems as application events with Amazon EventBridge or directly from software as a service (SaaS) applications with Amazon AppFlow.
Step 2
Process customer activity and detect the guest location and journey stage (for example, checking in) with AWS Step Functions.
Step 3
Infer the next best action by invoking AWS Lambda and Amazon SageMaker trained machine learning (ML) model.
Step 4
Amazon DynamoDB tables store customer check-in info, location, and recommended next best action, then triggers guest notifications with Amazon DynamoDB Streams.
Step 5
Use Amazon Pinpoint to notify guests about check in, room readiness, and other events over channels like email, SMS, push, or in-app messaging.
Step 6
The hotel’s mobile or web app or on-property guest service apps send requests through an Amazon API Gateway endpoint.
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.
-
Operational ExcellenceRead the Operational Excellence whitepaper
The reference architecture can be scripted using Amazon CloudFormation, added to your own development pipeline, and deployed in your cloud environment. Use Amazon CloudWatch to increase your observability with application and service-level metrics, personalized dashboards, and logs.
-
SecurityRead the Security whitepaper
With Amazon Cognito user pools, you can use identity pools to provide built-in user management and secure access to APIs. The Lambda back end only has access to the services they need with least privileged roles. The guest data in DynamoDB and Amazon Simple Storage Service (Amazon S3) is encrypted at rest.
-
ReliabilityRead the Reliability whitepaper
EventBridge and Amazon AppFlow are fully managed services that provide consistent throughput at scale. All the serverless components are highly available and automatically scale based on usage. We recommend DynamoDB cross-region deployment for higher availability.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
Serverless architectures help you provision the exact resources that the workload needs. Monitor for expected performance by using CloudWatch alarms and Lambda metrics. For unexpected traffic, configure DynamoDB on-demand; use provisioned mode for consistent traffic.
-
Cost OptimizationRead the Cost Optimization whitepaper
Serverless architectures provide a pay-per-value pricing model and scale based on demand. A good practice is to use AWS Budgets to create budgets for cost and usage governance. Create and use Cloud Intelligence Dashboards for comprehensive cost management and financial optimization.
-
SustainabilityRead the Sustainability whitepaper
By choosing serverless services, you are using only the resources that you need and therefore reducing impacts.
Implementation Resources
A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.
The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.
Related Content
[Title]
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.