What it is
Amazon Location Service is the AWS service for location features: maps, place search, routes, device position tracking and geofencing. It sits inside an AWS account like any other service, so location data stays with the rest of the application's data and is controlled with the same IAM permissions.
Two parts matter most for equipment tracking. A tracker stores the positions that devices report and keeps their history. A geofence collection holds boundaries drawn as polygons or circles; when a tracked position crosses into or out of one, the service emits an enter or exit event to Amazon EventBridge, where a rule can act on it.
How I use it
- In the pattern I build with, GPS fixes from Raspberry Pi trackers arrive through AWS IoT Core and are passed to an Amazon Location tracker.
- Each rental gets a geofence around its job site, and exit events reach EventBridge, where a Lambda function sends the alert.
- Position history supports trail replay alongside the full record of fixes kept in S3.
- Maps from the same service can draw the fleet on a dashboard inside the software the business already uses.
Geofencing by hand means checking every position against every boundary in your own code. Amazon Location Service does that evaluation as positions arrive and hands back a clean enter or exit event, so the business rule, such as alerting dispatch when a rented machine leaves its job site, is a few lines in a function rather than a geometry project.
Questions
What is a geofence?
A boundary on the map, such as a circle around a job site. When a tracked device crosses it, Amazon Location Service raises an enter or exit event that the rest of the system can act on.
Do I need Amazon Location Service to track GPS positions?
Not strictly. Positions can be stored and checked in your own code. The service saves writing and running the geofence checks and position history yourself.
Where do the positions come from?
From the devices. In the pattern I build with, a Raspberry Pi tracker with a cellular shield and GPS receiver sends its fixes to AWS IoT Core, which passes them on.