Guidance for Location-Based Customer Engagement on AWS
Overview
This Guidance demonstrates how leaders in the travel and hospitality industry can use the capabilities of Amazon Location Service to enhance their applications with location-based functionalities. Amazon Location provides a suite of features, including interactive maps, device trackers, and geofence collections, that developers can integrate into their applications. By incorporating these location-based capabilities, travel and hospitality organizations can deliver a more personalized and contextual user experience, such as triggering real-time messages and location-specific information to customers as they enter or exit predefined geofences. This can be around a hotel, resort, or tourist attraction. They can also monitor the movements of vehicles or assets and initiate events when they enter or exit designated areas, supporting various uses like automated notifications and route optimization.
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Well-Architected Pillars
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.
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.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages