Amazon Location Service offers three pricing plans that require no up-front commitment, and no minimum fee. You are only charged for what you use. Your application will use Amazon Location Service to make requests for various types of location information. You select one of the following pricing plans for each of the Amazon Location Service resources you create for your application. You can use multiple plans within the same account.

Request-Based Usage

So you can easily get started, this price plan offers an Amazon Location Service free tier for the first three months of Request-Based Usage. The Request-Based Usage pricing plan provides access to location data that is billed based on each request your application makes to the service. Beyond the Amazon Location Service free tier, you pay for the requests your application makes to the service. 

Amazon Location Service Free Tier for Request-Based Usage

You can evaluate Amazon Location Service using the free tier during your first three months of Request-Based Usage. During that time, you will not be billed for monthly request-based usage up to the levels defined in the table below. If your usage exceeds the free tier levels, you will be billed for any additional requests you use according to paid tier rates. You can only use the free tier for use cases that meet the summary of requirements below the table.

Capabilities Included monthly, for 3 months
Maps 500,000 Map tiles retrieved (Vector or Raster)
Places

10,000 Addresses geocoded

10,000 Positions reverse-geocoded

Routes 10,000 Routes calculated
Tracking

200,000 Positions written

10,000 Batch position reads

5,000 Devices deleted

Geofencing

200,000 Positions evaluated

10,000 Geofences created, deleted or described

10,000 Geofence list requests
Service Resources

10,000 Resource create, read, update, delete, or list requests

  • Summary of requirements for this plan:

    You may only use this price plan for applications where at least one of the following is true:

    • Your application uses Amazon Location Service Tracking or Geofencing without using Amazon Location Service Maps, Places, or Routes. (Note, for this use case, you may use this price plan or any of the other price plans.)
    • Your application is used for any purpose other than tracking, routing, or route-optimizing mobile assets (such as vehicles, cargo, employees, or other mobile objects with mobile or tracking devices) that you use in your business. Mobile devices used by consumers for personal use are not considered mobile assets. For example, you may use this price plan for:
      • An application offering consumers a curbside pickup service where your business can expedite service and ensure freshness based on consumer proximity to your business location.
      • A geomarketing application that pushes advertisements to consumers on their mobile devices when they are near your store.
      • An application on consumer mobile devices that helps them locate and obtain driving directions to your nearest store.
      • A consumer application that helps users find each other using their mobile device.
    Please see the full requirements for this price plan in the Amazon Location Service section of the AWS Service Terms. For additional information, see the Pricing section of the Amazon Location Service FAQs.

Learn more about how Amazon Location Service API Requests are defined and measured in the Definitions and Details here.

Request-Based Usage Paid Tier

After the three-month free-tier period is complete, or if you exceed the free tier limits defined above, you pay for the requests your application makes to the service outlined in the table below. You can only use this plan for use cases that meet the summary of requirements below the table.

  • Maps
  • Places
  • Routing
  • Tracking
  • Geofencing
  • Service Resources
  • Maps
  • Places
  • Routing
  • Tracking

  • * Per batch of up to 500 positions read. 

  • Geofencing

  • * Evaluation of a single position against all geofences in a geofence collection. 
    ** Applies only to geofences that persist longer than 1 month. 
  • Service Resources
  • Summary of requirements for this plan:

    You may only use this price plan for applications where at least one of the following is true:

    • Your application uses Amazon Location Service Tracking or Geofencing without using Amazon Location Service Maps, Places, or Routes. (Note, for this use case, you may use this price plan or any of the other price plans.)
    • Your application is used for any purpose other than tracking, routing, or route-optimizing mobile assets (such as vehicles, cargo, employees, or other mobile objects with mobile or tracking devices) that you use in your business. Mobile devices used by consumers for personal use are not considered mobile assets. For example, you may use this price plan for:
      • An application offering consumers a curbside pickup service where your business can expedite service and ensure freshness based on consumer proximity to your business location.
      • A geomarketing application that pushes advertisements to consumers on their mobile devices when they are near your store.
      • An application on consumer mobile devices that helps them locate and obtain driving directions to your nearest store.
      • A consumer application that helps users find each other using their mobile device.
    Please see the full requirements for this price plan in the Amazon Location Service section of the AWS Service Terms. For additional information, see the Pricing section of the Amazon Location Service FAQs.

Learn more about how Amazon Location Service API Requests are defined and measured in the Definitions and Details here.

Mobile Asset Tracking

The Mobile Asset Tracking pricing plan provides a predictable and fixed monthly price per active mobile asset. You are only charged for the mobile assets that have reported a position to the service that month. For more information on how mobile assets are defined and counted by Amazon Location Service, click here. You can only use this plan for use cases that meet the summary of requirements below the table. 

Mobile Asset Tracking pricing

  • Mobile Asset Tracking
  • Geofencing
  • Places
  • Service Resources
  • Mobile Asset Tracking
  • Geofencing
  • Places
  • Service Resources

*  Geocodes and reverse-geocodes that are not stored are included in the per-asset allowance. Stored results are billed separately.
**  Amazon Location Service Route requests are not included in this plan.
*** The price applies to one provider. If you want to use multiple providers in the same application, you will be charged once for each provider and are required to report your devices to one tracker resource for each provider.  
  • Summary of requirements for this plan:

    You may only use this price plan for applications where at least one of the following is true:

    • Your application uses Amazon Location Service Tracking or Geofencing without using Amazon Location Service Maps, Places, or Routes. (Note, for this use case, you may use this price plan or any of the other price plans.)
    • Your application is tracking, but not routing or route-optimizing, mobile assets (such as vehicles, cargo, employees, or other mobile objects with mobile or tracking devices) that you use in your business. Mobile devices used by consumers for personal use are not considered mobile assets. For example, you may use this price plan for:
      • An application that helps a company track (but not route or route-optimize) its inventory, delivery personnel, or maintenance vehicles. 
    Please see the full requirements for this price plan in the Amazon Location Service section of the AWS Service Terms. For additional information, see the Pricing section of the Amazon Location Service FAQs.

Learn more about how Amazon Location Service API Requests are defined and measured in the Definitions and Details here.

Mobile Asset Management

The Mobile Asset Management pricing plan provides a predictable fixed monthly price per active mobile asset. You are only charged for the mobile assets that have reported a position to the service that month. For more information on how mobile assets are defined and counted by Amazon Location Service, click here. You can only use this plan for use cases that meet the summary of requirements below the table.

Mobile Asset Management pricing

  • Mobile Asset Management
  • Geofencing
  • Places
  • Service Resources
  • Mobile Asset Management
  • Geofencing
  • Places
  • Service Resources
* Geocodes and reverse-geocodes that are not stored are included in the per-asset allowance. Stored results are billed separately.
** You may only use one provider for each price plan. If you want to use multiple providers in the same application, you will be charged once for each provider and are required to report your devices to one tracker resource for each provider.
  • Summary of requirements for this price plan:

    You may only use this price plan for applications where at least one of the following is true:

    • Your application uses Amazon Location Service Tracking and Geofencing without using Amazon Location Service Maps, Places, or Routes. (Note, for this use case, you may use this price plan or any of the other price plans.)
    • Your application is tracking, routing or route-optimizing mobile assets (such as vehicles, cargo, employees, or other mobile objects with mobile or tracking devices) that you use in your business. Mobile devices used by consumers for personal use are not considered mobile assets. For example, you may use this price plan for: 
      • An application that routes your company’s vehicles or staff, or optimizes your company’s delivery routes. 
    Please see the full requirements for this price plan in the Amazon Location Service section of the AWS Service Terms. For additional information, see the Pricing section of the Amazon Location Service FAQs.

Learn more about how Amazon Location Service API Requests are defined and measured in the Definitions and Details here.

  • Amazon Location Service Requests Definitions and Details

    Map tile: a request to retrieve a piece, or “tile,” of a larger digital map. When your application displays a map, it is showing a collection of map tiles. Amazon Location Service uses two types of map tiles: raster tiles, which are 256 x 256 pixel map images; and vector tiles, which represent the geographical features of a small map area.

    Address geocoded: a request to convert a text description of a location, such as a street address or a point of interest, to a set of latitude and longitude coordinates.

    Position reverse-geocoded: a request to convert latitude and longitude coordinates to a readable street address or place name.

    Stored result: a request to store and reuse the addresses or latitude and longitude coordinates that are the results of geocoding or reverse-geocoding operations.

    Geofence: requests to create, delete, or describe a geofence. A geofence is a geographical boundary defined on a map. For example, a retail chain could create geofences around their store locations so they can send customers a coupon when they are near a store. A “geofence-month” represents storage of a geofence definition for a period of one month in Amazon Location Service.

    Position writes: a request for Amazon Location Service to record the location of a tracked entity in your account. For example, a fitness application can periodically record the location of an athlete during a run by using position write requests. Batch position writes are requests to record multiple locations for one or more tracked entities with timestamps. Each element requested in a batch call counts as a request.

    Position reads: a request to retrieve the location of a tracked entity, for instance to show the location of visitors using a ski resort’s mobile application. Batch position reads are requests to retrieve multiple locations for one or more tracked entities with timestamps. Each element requested in a batch call counts as a request.

    Position evaluated: a request for Amazon Location Service to determine the position of a tracked entity in relation to a set of geofences, and to send events to Amazon EventBridge if the tracked entity enters or exits a geofence. For example, a pizza chain’s application could determine that its delivery driver has crossed a geofence that is a half-mile from their customer, and send the customer an alert that their order is about to arrive.

    Route calculated: a request for Amazon Location Service to calculate a route (travel time, distance, and geometry) to travel between a departure location and one or more destinations.

    Service resources: requests to create, read, update, delete, or list the Amazon Location Service resources, such as a Map resources (used to retrieve map tiles in a specific style), Place Index resources (used to perform geocoding, reverse geocoding, and point-of-interest searches),  Route Calculator resources (used to request route calculations), Geofence Collection resources (used to store geofences and evaluate positions against them), and Tracker resources (used to store and retrieve device positions). Requests to link and unlinking resources, such as trackers and geofences, is also considered a resource update.

    Object resources: requests to list, describe, or delete objects within a resource such as devices in a Tracker resource or Geofences in a geofence collection. 

     

Pricing examples

  • Pricing example 1: Web-based map application (with free tier)

    A municipality’s public website features a map that is used by 10,000 visitors every month. On average, each map use requires 80 map tiles and geocodes one address. In total, this map requests 800,000 map tiles and makes 10,000 geocoding requests on a monthly basis. 500,000 tiles and 10,000 geocoding requests per month are covered by the AWS Free Tier in the first three months.

    First 3 months

    Maps charges 800,000 tiles – 500,000 included tiles = 300,000
    300,000 / 1,000 x $0.04 = $12.00
    Geocoding charges (10,000 requests – 10,000 included requests) / 1,000 x $0.5 = $0.00
    Total monthly Amazon Location Service charges  $12.00 + $0.00 = $12.00

    After first 3 months

    Maps charges  800,000 tiles / 1,000 x $0.04 = $32.00
    Geocoding charges 10,000 requests / 1,000 x $0.5 = $5.00
    Total monthly Amazon Location Service charges  $32.00 + $5.00 = $37.00
  • Pricing example 2: Asset tracking application

    A freight shipment company built an asset tracking application with Amazon Location Service to improve visibility into the location of its shipping containers around the world. Accordingly, the company’s developer chose the Mobile Asset Tracking pricing plan in Amazon Location Service when setting up tracking. The application tracks 100 shipping containers, and each shipping container writes its position every five minutes. Ten employees monitor the position of shipping containers on a map. Each employee views the map five times per day. During each view, the application requests and displays an average of 80 map tiles, and requests two address geocodes, four current position reads, and one historical position read. The number of user visits per month is 1,500 (10 employee users x 5 visits/day x 30 days).

    Maps charges 80 tiles x 1,500 visits = 120,000 tiles
    Geocoding usage 2 geocodes x 1,500 visits = 3,000 geocodes
    Tracking (position writes) 100 shipping containers x 12 writes / hour x 24 hours /day x 30 days / month = 864,000 position writes per month
    Tracking (position read requests) 5 position reads x 1,500 visits = 7,500 position reads
    Total Amazon Location Service requests 120,000 + 3,000 + 864,000 + 7,500 = 994,500 requests
    Under the Mobile Asset Tracking plan, 100 assets would have 2.5 million included requests (25,000 requests x 100 assets). As a result, the 994,500 total monthly requests for this application would be covered by the included requests for the Mobile Asset Tracking plan. This asset tracking application would cost $150 in Amazon Location Service charges per month.
    Total monthly Amazon Location Service charges for 100 tracked assets 100 x $1.50 = $150.00
  • Pricing example 3: Asset management application

    A ride-sharing company has a dispatch application that tracks and routes vehicles to pick up customers. The company’s developer selects the Mobile Asset Management pricing plan when creating the Tracker, Router, and other service resources for this application. There are 100 vehicles, and each vehicle writes its position every 30 seconds. Customers request new pickups every 10 minutes on average, and each new pickup generates an average of 10 routing requests from the dispatch application (one for each available vehicle, to determine the closest vehicle, and to dispatch it to the customer). At the same time, from the customer-facing mobile application, each pickup request generates an average of two address geocode requests, and 40 map tile requests. Ten employees in the office monitor the position of the vehicles using the dispatch application. Each employee views the map five times per day. During each view, the application requests and displays an average of 80 map tiles, and requests two address geocodes, four current position reads, and one historical position read.

    The total number of pickup requests per month is 4,320 (6 requests / hour x 24 hours / day x 30 days / month).

    The number of user employee visits to the dispatch application per month is 1,500 (10 employee users x 5 visits / day x 30 days / month).

    Maps usage

    80 tiles x 1,500 visits = 120,000 tiles (employees)

    40 tiles x 4,320 pickups = 172,800 tiles (pickups)

    Geocoding usage

    2 geocodes x 1,500 visits = 3,000 geocodes (employees)

    2 geocodes x 4,320 pickups = 8,640 geocodes (pickups)

    Routes 10 routes x 4,320 pickups = 43,000 routes (pickups)
    Tracking (position writes) 100 vehicles x 120 writes/hour x 24 hours/day x 30 days/month = 8,640,000 position writes
    Tracking (position reads) 5 position reads x 1,500 visits = 7,500 position reads
    Total Amazon Location Service requests 120,000 + 172,800 + 3,000 + 8,640 + 43,200 + 8,640,000 + 7,500 = 8,995,140 requests
    Under the Mobile Asset Tracking plan, 100 assets would have 25 million included requests (250,000 requests x 100 assets). As a result, the 8,995,140 total monthly requests for this application would be covered by the included requests for the Mobile Asset Management plan. This asset tracking application would cost $1,500 in Amazon Location Service charges.
    Total monthly Amazon Location Service charges for 100 tracked assets 100 x $15.00 = $1,500.00
Check out the FAQs
Check out the FAQs

Learn more about Amazon Location Service on the FAQs page.

Learn more 
Sign up for a free account
Sign up for a free account

Instantly get access to the AWS Free Tier. 

Sign up 
Start building in the console
Start building in the console

Get started building with Amazon Location Service in the AWS Management Console.

Sign in