Pricing in Preview

Amazon Location Service is in Preview. During the Preview period, you will not incur Amazon Location Service charges for the use of the service. You may incur fees for the use of other AWS services such as Amazon EventBridge, AWS Lambda, and Amazon CloudWatch.

Amazon Location Service provides an easy way for developers to add location-based service capabilities to their applications. With the service, you can easily build applications that provide maps and points of interest, recommend routes, track assets, trigger actions based on location, and convert street addresses into geographic coordinates. To do this, your application will use Amazon Location Service “resources" 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.

Pricing plans

All three Amazon Location Service pricing plans require no up-front commitment, and no minimum fee. You are only charged for what you use. You can use multiple plans within the same account, but you only use one of these plans with each individual application. AWS requires you to use one of the Mobile Asset plans detailed below for certain applications. The pricing plans are:

  • Request-Based Usage – Select this plan to provide maps and other location information for external users such as customers, or internal applications that don’t involve tracking or routing of assets you control. With this plan, you are billed for each request your application makes to the service, so your costs scale proportionally with usage of your application’s location-based capabilities. You may not select this plan if you are using Amazon Location Service Maps or Places for an application that tracks mobile assets over which you have operational control. Learn more »
  • Mobile Asset Tracking – Select this plan only for your applications that use Amazon Location Service Maps or Places for tracking of mobile assets, but do not perform routing or route optimization. With this plan you are billed a predictable, fixed monthly price per asset, with 25,000 location data requests per asset included. Learn more »
  • Mobile Asset Management – Select this plan only for your applications that use Amazon Location Service Maps or Places for tracking, AND routing or route optimization of mobile assets. With this plan you are billed a predictable, fixed monthly price per asset, with 250,000 location data requests per asset included. Learn more »

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. For example, you would use Request-Based Usage when you want to display a map on your public website, provide customers directions to your closest store, or send location-based marketing offers to your mobile app users. You may not select this plan if you are using Amazon Location Service Maps or Places for an application that tracks mobile assets, over which you have operational control.

To opt into Request-Based Usage plan and get started, you go the Amazon Location Service console or API to create service resources to access maps, perform geocoding, track entities, and store geofences. As part of the process to create a resource, you specify “Request-Based Usage” as the pricing plan.1

Amazon Location Service offers a free tier for the first three months of Request-Based Usage, so you can easily get started at no cost. See below for details.

Beyond the free tier, you pay for the requests your application makes to the service.

  • Click to see the definitions of the different requests.

    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, 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.

    Position writes: a request for Amazon Location 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 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.

    Routes calculated: a request for Amazon Location Service to provide a route to travel between two locations.

    Service resources: requests to create, read, update, delete, or list the Amazon Location Service resources, which include the following. A Map resource is used to retrieve map tiles in a specific style. A Place Index resource is used to perform geocoding, reverse geocoding, and point-of-interest searches. A Geofence Collection resource is a group of geofences. A Tracker resource is used to receive and retrieve position locations and timestamps from the things you are tracking. A Router resource is used to compute routes for travel between two locations.

1 Tracking your organization’s mobile assets with the Request-Based Usage pricing plan would be a violation of the Amazon Location terms of service.

AWS Free Tier for Request-Based Usage

You can evaluate Amazon Location Service at no cost 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 resources you use. After the three-month free tier period, you will be billed according to paid tier rates. You can learn more about the AWS Free Tier here.

Capabilities Included monthly usage, for 3 months
Maps 500k Map tiles
Places

10k Addresses geocoded

10k Positions reverse-geocoded

Tracking

200k Position writes

10k Batch position reads

Geofencing

200k Positions evaluated

10k Geofences created, deleted or described

10k Geofence list requests
Service Resources 10k requests to create, read, update, delete, or list resources

Request-Based Usage Paid Tier

After the three-month free-tier period is complete, you pay for the requests your application makes to the service, including the following. 

Capabilities

Requests

Price per 1,000

Maps

Map tiles retrieved

$0.04

Places

Addresses geocoded

Addresses geocoded (stored result)

Positions reverse-geocoded

Positions reverse-geocoded (stored result)

$0.50

$4.00

$0.50

$4.00

Tracking

Position writes

Batch position reads1

$0.05

$0.05

Geofencing

Positions evaluated2

Geofences created, deleted or described

Geofence list

Geofence-months3

$0.20

$0.05

$0.05

$0.20

Service Resources

Resource create, read, update, delete or list 

$0.01

(1) Per batch of up to 500 positions read
(2) Evaluation of a single position against all geofences in a geofence collection
(3) Applies only to geofences that persist longer than 1 month
(4) Pricing shown is for the US East (N. Virginia) AWS Region. Pricing for the other regions will be provided when the service is generally available.

Mobile Asset Tracking

Many companies and organizations have applications to keep track of the location of mobile assets, such as fleets of maintenance vehicles or valuable inventory, as the assets move through the world.

The Mobile Asset Tracking plan provides you the capability to keep track of your enterprise’s mobile assets, with a predictable fixed monthly price per active mobile asset and a large number of included requests. For this plan, a mobile asset is defined as any mobile object over which you can exercise operational control in support of your business (e.g., a shipping container with a GPS tracker or a point-of-sale tablet). Amazon Location Service counts a mobile asset as active for billing if the asset reports its location to the service in a given month. For more information on how mobile assets are defined and counted by Amazon Location, click here.

The Mobile Asset Tracking plan is required if you are doing all of the following as part of your use case: tracking mobile assets, and using maps or places (geocoding or reverse geocoding).

Note: Entities you do not control are not considered mobile assets. In the case of external end-users of your mobile application, to whom you are sending location based marketing offers for example, you would use Request-Based Usage pricing plan. For routing and route optimization of mobile assets, you must select Mobile Asset Management.

To opt into the Mobile Asset Tracking plan and get started, you go the Amazon Location Service console or API to create service resources to access maps, perform geocoding, track entities, and store geofences. As part of the process to create a resource, you specify “Mobile Asset Tracking” as the pricing plan.2

Mobile Asset Tracking pricing

Capabilities Included usage per monthly active asset  Price per month
Mobile Asset Tracking 25,000 Maps, Places, Tracking, and Geofencing requests. Additional usage is charged at $1.50 per 25,000 requests or a portion thereof. $1.50 per asset 
Geofencing Geofence-month $0.20 per 1,000 geofences

Pricing shown is for the US East (N. Virginia) AWS Region. Pricing for the other regions will be provided when the service is generally available.

2 Tracking your organization’s mobile assets with the Request-Based Usage pricing plan would be a violation of the Amazon Location terms of service. 

Mobile Asset Management

Many organizations have applications that provide routes and directions for their vehicles or staff, or optimize the routes for enterprise assets in order to help them accomplish their tasks.

The Mobile Asset Management plan provides you the capability to route mobile assets that you control, optimize their routes, and also track them. For this plan, a mobile asset is defined as any mobile object over which you can exercise operational control in support of your business. Routing is when you are providing route calculations for a mobile asset, and route optimization is when you use a software application to calculate the order of destinations or routes. The Mobile Asset Management plan has a predictable monthly price per asset, and a large number of included requests. Amazon Location Service counts a mobile asset as active for billing if the asset reports its location to the service in a given month. For more information on how mobile assets are defined and counted by Amazon Location, click here

The Mobile Asset Management plan is required if you are doing all of the following as part of your use case: tracking mobile assets, using maps or places (geocoding or reverse geocoding), and performing routing or route optimization.

Note: Entities you do not control are not considered mobile assets. In the case of external end-users of your mobile application, to whom you providing routing, for example, you would use Request-Based Usage pricing plan.

To opt into the Mobile Asset Management plan and get started, you go to the Amazon Location Service console or API to create service resources to access maps, perform geocoding, route or track entities, and store geofences. As part of the process to create a resource, you specify “Mobile Asset Tracking” as the pricing plan.3

Mobile Asset Management pricing

Capabilities Included usage per monthly active asset  Price per month
Mobile Asset Management 250,000 Maps, Places, Tracking, Geofencing, and Routing requests. Additional usage is charged at $15.00 per 250,000 requests or a portion thereof. $15.00 per asset
Geofencing Geofence-month $0.20 per 1,000 geofences

Pricing shown is for the US East (N. Virginia) AWS Region. Pricing for the other regions will be provided when the service is generally available.

Performing routing or route optimization for your organization’s mobile assets with the Request-Based Usage pricing plan would be a violation of the Amazon Location terms of service.

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. Because the shipping containers are under the freight company’s operational control, they are considered mobile assets. 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 writes) 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 vehicles are under the company’s operational control, so they are considered mobile assets. They are being routed, so the Mobile Asset Management plan applies. 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)

    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 + 8,640,000 + 7,500 = 8,951,940 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,951,940 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