AutoGineer
Generated banner for Amazon Location Service
Generated logo for Amazon Location Service

Amazon Location Service

AWS LabsOfficialCreated by aws-geospatialDistributed by AWS Labs

  • Skill
  • Tool integration
  • Cloud and DevOps
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Integrates Amazon Location Service APIs for AWS applications. Use this skill when users want to add maps (interactive MapLibre or static images); geocode addresses to coordinates or reverse geocode coordinates to addresses; calculate routes, travel times, or service areas; find places and businesses through text search, nearby search, or autocomplete suggestions; retrieve detailed place information including hours, contacts, and addresses; monitor geographical boundaries with geofences; or track device locations. Covers authentication, SDK integration, and all Amazon Location Service capabilities.
— the description by aws-geospatial

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Amazon Location Service provides a suite of geospatial APIs for web and mobile applications. This skill covers the integration of maps, geocoding, routing, places search, geofencing, and device tracking. It emphasizes the use of the bundled JavaScript client for web development and promotes resourceless API operations to simplify deployment. The skill also provides guidance on authentication via IAM or API keys, and distinguishes between interactive address input and bulk postal address validation using the Jobs API.

What it does

  • Provides interactive maps using MapLibre and static map images.
  • Converts addresses to coordinates (geocoding) and coordinates to addresses (reverse geocoding).
  • Calculates routes, travel times, and service areas with traffic estimation.
  • Searches for places, businesses, and points of interest with autocomplete functionality.
  • Monitors geographical boundaries with geofences and tracks device locations.
  • Validates and standardizes addresses in bulk against authoritative postal data.

When to use it

  • When building location-aware web or mobile applications on AWS.
  • When you need to implement maps, routing, or place search functionality.
  • When you need to verify and standardize large datasets of addresses in the US, CA, UK, or AU.
  • When you need to track device locations or monitor entry/exit from geofenced areas.
  • When migrating from other mapping providers to Amazon Location Service.

Advantages

  • Supports resourceless API operations to reduce infrastructure management.
  • Provides a bundled JavaScript client for simplified web integration.
  • Offers flexible authentication options including API keys for public applications.
  • Includes specialized APIs for bulk address validation and postal standardization.
  • Integrates seamlessly with other AWS services and SDKs.

Usage examples

“How do I implement an address autocomplete field in my React app using Amazon Location Service?”
The agent provides a guide on using the Autocomplete API, emphasizing the use of Address.Label for display and GetPlace for retrieving full details upon selection.
“I need to validate a large database of customer addresses in the UK. How should I do this?”
The agent explains the use of the asynchronous Jobs API (StartJob with ValidateAddress) for bulk processing, noting that it provides postal-authority verdicts.
“How do I initialize a map in my web application?”
The agent provides instructions on using MapLibre with a direct URL to the map style descriptor and setting validateStyle to false for performance.
“What are the best practices for securing my map implementation on a public website?”
The agent recommends using API Keys with restricted AllowActions and AllowResources, rather than exposing IAM credentials.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/awslabs/amazon-location-service/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip amazon-location-service.zip -d .agents/skills

Documentation by aws-geospatial

Overview

Amazon Location Service provides geospatial APIs for maps, geocoding, routing, places search, geofencing, and tracking. Prefer the bundled JavaScript client (@aws/amazon-location-client) for web development and use resourceless API operations to avoid managing AWS resources.

When to Use This Skill

Use this skill when:

  • Building location-aware web or mobile applications

  • Working with Amazon Location Service projects

  • Implementing maps, geocoding, routing, or places search

  • Adding geofencing or device tracking functionality

  • Integrating geospatial features into AWS applications

Do NOT use this skill for:

  • Google Maps, Mapbox, or Leaflet-with-OSM projects (unless migrating to Amazon Location)

  • Generic GIS operations without AWS context

  • Non-AWS geospatial services

Amazon Location Service API Overview

Places (SDK: geo-places, JS: @aws-sdk/client-geo-places)

  • Geocode (Forward/Reverse): Convert addresses to coordinates and vice versa

  • Search (Text/Nearby): Find points of interest with contact and hours info

  • Autocomplete: Predict addresses based on user input

  • Suggest: Predict places and points of interest based on partial or misspelled user input

  • Get Place: Retrieve place details by place ID

Jobs (SDK: location, JS: @aws-sdk/client-location)

  • Address Validation: Verify and standardize addresses in bulk with the asynchronous Jobs API (StartJob with Action ValidateAddress, then GetJob/ListJobs/CancelJob). It adds what Geocode lacks — a postal-authority verdict (ValidationGranularity, Mailable/Locatable, per-component StatusDetail), not just coordinates. Coverage is US, CA, UK, and AU only; for other countries use Geocode.

Maps (SDK: geo-maps, JS: @aws-sdk/client-geo-maps)

  • Dynamic Maps: Interactive maps using tiles with MapLibre rendering

  • Static Maps: Pre-rendered, non-interactive map images, good for including an image into a web page, or for thumbnail images

Routes (SDK: geo-routes, JS: @aws-sdk/client-geo-routes)

  • Route calculation with traffic and distance estimation

  • Service area/isoline creation

  • Matrix calculations for multiple origins/destinations

  • GPS trace alignment to road segments

  • Route optimization (traveling salesman problem)

Geofences & Trackers (SDK: location, JS: @aws-sdk/client-location)

  • Geofences: Detect entry/exit from geographical boundaries

  • Trackers: Current and historical device location tracking

API Keys (SDK: location, JS: @aws-sdk/client-location)

  • API Keys: Grant access to public applications without exposing AWS credentials

Common Mistakes

Avoid these frequent errors:

  1. Using Title instead of Address.Label for display: In Autocomplete results, always display Address.Label. The Title field may show components in reverse order and is not suitable for user-facing text.

  2. Using GetStyleDescriptor API for map initialization: MUST use direct URL passing to MapLibre (https://maps.geo.{region}.amazonaws.com/v2/styles/Standard/descriptor?key={apiKey}) instead of making GetStyleDescriptor API calls. The direct URL method is required for proper map rendering.

  3. Forgetting validateStyle: false in MapLibre config: Always set validateStyle: false in the MapLibre Map constructor for faster map load times with Amazon Location styles.

  4. Mixing resource-based and resourceless operations: When possible, prefer resourceless operations (direct API calls without pre-created resources) for simpler deployment and permissions.

  5. Inconsistent API operation naming: Use the format service:Operation when referencing APIs (e.g., geo-places:Geocode, geo-maps:GetStyleDescriptor). SDK clients use @aws-sdk/client-* format.

  6. Not handling nested Address objects correctly: The Address object from GetPlace contains nested objects (Region.Code, Region.Name, Country.Code2, etc.), not flat strings. Access nested properties correctly.

  7. Wrong action names in API Key permissions: API key AllowActions use geo-maps:, geo-places:, geo-routes: prefixes (e.g., geo-places:Geocode, geo-routes:CalculateRoutes). Do NOT use SDK client names (@aws-sdk/client-geo-places) or IAM-style actions. See the Authentication and Permissions section for the complete list.

Defaults

Use these default choices unless the user explicitly requests otherwise:

  • JavaScript SDK: Bundled client (CDN) for browser-only apps; npm modular SDKs (@aws-sdk/client-geo-*) for React and build tool apps

  • API operations: Resourceless for Maps/Places/Routes (Geofencing/Tracking always require pre-created resources)

  • Authentication: API Key for Maps/Places/Routes; Cognito for Geofencing/Tracking

  • Map style: Standard

  • Coordinate format: [longitude, latitude] (GeoJSON order)

Override: User can specify "use Cognito for Maps/Places/Routes" or "use bundled client for React".

API Selection Guidance

Choose the right API for your use case:

Address Input (interactive forms)

  • Autocomplete → Type-ahead in address forms (partial input: "123 Main")

  • GetPlace → Get full details after user selects autocomplete result (by PlaceId)

  • Geocode → Resolve a complete user-typed address to coordinates. Returns coordinates, a matched label, and match quality (MatchScores overall + per-component, AddressNumberCorrected) synchronously in one call — but no postal-deliverability verdict or standardized output.

Address Validation (verify & standardize)

  • StartJob (Action ValidateAddress) → Verify and standardize addresses in bulk against authoritative postal data; async Jobs API with Parquet input/output in Amazon S3. Coverage: US, CA, UK, AU only; for other countries use Geocode.

  • GetJob / ListJobs / CancelJob → Track, enumerate, and cancel validation jobs

  • Choose the Jobs API when you need a postal-authority verdict (ValidationGranularity, Mailable/Locatable, per-component StatusDetail) or bulk throughput. For a single ad-hoc check of whether one address resolves and how well it matched, the synchronous Geocode MatchScores is the right tool — do not stand up a job. See the address-verification reference.

Finding Locations

  • SearchText → General text search ("pizza near Seattle")

  • SearchNearby → Find places near a coordinate (restaurants within 5km)

  • Suggest → Predict places/POIs from partial or misspelled input

  • Autocomplete → Address-specific predictions (not for general POI search)

Geocoding

  • Geocode (Forward) → Address string → Coordinates

  • ReverseGeocode → Coordinates → Address

Maps

  • Dynamic Maps (tiles + MapLibre) → Interactive maps requiring pan, zoom, markers

  • Static Maps (image) → Non-interactive map images for thumbnails or email

Routing

  • CalculateRoutes → Single route between origin and destination

  • CalculateRouteMatrix → Multiple origins/destinations travel times

  • CalculateIsolines → Service areas (all locations reachable within time/distance)

LLM Context Files

When you need detailed API parameter specifications or service capabilities not covered in the reference files, fetch these llms.txt resources:

Key Guidance for Better Recommendations

Prefer the Bundled JavaScript Client for Web Development

For convenient web application development, Amazon Location Service provides a bundled JavaScript client that simplifies integration and provides optimized functionality without custom bundling. This bundled client includes all libraries required to build client side web applications with Amazon Location Service.

Features included in the bundled client:

  • Enables direct pre-bundled dependency inclusion without custom bundle / build

  • Simplified authentication and API integration

  • TypeScript support with comprehensive type definitions

  • Support for all Amazon Location SDKs

Included SDKs and Libraries:

Resources:

Prefer Resourceless Operations

Amazon Location Places, Maps and Routes services offer both resource-based and resourceless API operations. Resourceless operations are often simpler and more appropriate for many use cases.

Resource-based operations require you to:

  • Create and configure Amazon Location Service resources (maps, place indexes, route calculators)

  • Manage resource lifecycle and permissions

  • Handle resource naming and organization

Resourceless operations allow you to:

  • Make API calls directly without pre-creating resources

  • Reduce deployment complexity

  • Simplify IAM permissions and API Key permissions

Authentication and Permissions

When discussing permissions for Amazon Location Places, Maps and Routes services, always include both IAM permissions and API Key permissions in your guidance. If the type of application being developed is clear, recommend the appropriate authorization tool as described below:

IAM Permissions - Recommended for server-side applications and AWS SDK usage:

  • Used with AWS credentials (access keys, roles, etc.)

  • Provide fine-grained access control

  • Required for resource management operations

API Key Permissions - Alternative authentication method, especially useful for client-side applications or applications deployed to unauthenticated (public) users:

  • Simplified authentication without exposing AWS credentials

  • Can be configured with specific allowed operations

  • Useful for web and mobile applications

  • Supports both resource-based and resourceless operations

  • Enables faster subsequent map loads through CDN caching

API Key Action Names - API keys use their own action naming convention. Do NOT use SDK client names or IAM action names — they will be rejected.

Resourceless API key actions (recommended):

ServiceAllowActionsAllowResources
Mapsgeo-maps:GetTile, geo-maps:GetStaticMaparn:aws:geo-maps:REGION::provider/default
Placesgeo-places:Autocomplete, geo-places:Geocode, geo-places:ReverseGeocode, geo-places:SearchText, geo-places:SearchNearby, geo-places:Suggest, geo-places:GetPlacearn:aws:geo-places:REGION::provider/default
Routesgeo-routes:CalculateRoutes, geo-routes:CalculateRouteMatrix, geo-routes:CalculateIsolines, geo-routes:OptimizeWaypoints, geo-routes:SnapToRoadsarn:aws:geo-routes:REGION::provider/default

Do NOT use legacy geo: prefixed actions (e.g., geo:GetMap*, geo:CalculateRoute) — these are for pre-created resources only and will not work with resourceless APIs.

LocationClient Setup

Geofencing and Tracking use LocationClient (@aws-sdk/client-location). These are resource-based operations — you MUST create resources (trackers, geofence collections) before using them.

import { LocationClient } from "@aws-sdk/client-location";

// Server-side: uses IAM credentials from environment/role
const client = new LocationClient({ region: "us-east-1" });
// Client-side: uses Amazon Cognito
import { LocationClient } from "@aws-sdk/client-location";
import { fromCognitoIdentityPool } from "@aws-sdk/credential-providers";

const client = new LocationClient({
  region: "us-east-1",
  credentials: fromCognitoIdentityPool({
    identityPoolId: "us-east-1:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    clientConfig: { region: "us-east-1" },
  }),
});

MCP Server Integration

Integrates with the AWS MCP Server (Apache-2.0 license) which provides access to AWS documentation, API references, and direct API interactions. See the Getting Started Guide for setup and credential configuration. To use a non-default region, add "--metadata", "AWS_REGION=<your-region>" to your MCP config args.

Additional Resources

Reference Files

Load these resources as needed for specific implementation guidance:

  • Address Input - Create effective address input forms for users with address type ahead completion improving input speed and accuracy

  • Address Verification - Verify and standardize addresses in bulk against authoritative postal data using the asynchronous Jobs API (StartJob with Action ValidateAddress), before persisting to databases or taking downstream actions

  • Calculate Routes - Calculate routes between locations with customizable travel options and display them on maps

  • Device Tracking - Track device locations in real time and query position history

  • Dynamic Map Rendering - Render dynamic maps with MapLibre

  • Google Maps Migration (Android) - Migrate Android application from Google Maps SDK for Android to Amazon Location Service

  • Google Maps Migration (iOS) - Migrate iOS application from Google Maps SDK for iOS to Amazon Location Service

  • Google Maps Migration (JavaScript) - Migrate JavaScript web application from Google Maps API to Amazon Location Service

  • Places Search - Search for places or points of interest

  • Web JavaScript - Integrate Amazon Location services into web browser applications

  • Zone Alerts - Monitor device positions against geographic boundaries and react to zone entry or exit

Files

references/address-input.md

Address Input

Audience Note: Keywords MUST, SHOULD, MAY in this document indicate requirements for agent recommendations to users, following RFC 2119.

Create effective address input forms with type-ahead completion that improves input speed and accuracy using Amazon Location Service Places APIs.

Distinction from Address Verification: This reference covers the interactive UI/UX of collecting a single address from a user (autocomplete, type-ahead, and resolving a typed address to coordinates). It is NOT postal address validation. To verify and standardize addresses against authoritative postal data — producing a match-confidence verdict and per-component status — use the asynchronous Jobs API (StartJob with Action ValidateAddress); see the address-verification reference. Geocode returns coordinates and a matched label, not a postal-deliverability verdict.

Table of Contents

  • Overview

  • Complete Implementation Flow

  • API Details

  • Code Examples

  • Error Handling

  • Best Practices

Overview

Address input forms SHOULD implement this three-stage flow:

  1. Autocomplete - Type-ahead suggestions as user types

  2. GetPlace - Fetch complete details when user selects a suggestion

  3. Geocode - Resolve the address to coordinates if the user types a complete address without selecting a suggestion

Complete Implementation Flow

// Stage 1: User types in address field → Autocomplete
// Stage 2: User selects suggestion → GetPlace
// Stage 3: User submits without selection → Geocode (resolve to coordinates)

// HTML Structure
<input id="address-input" type="text" placeholder="Enter address">
<div id="suggestions"></div>
<button id="submit">Submit</button>

API Details

Autocomplete

Purpose: Provide type-ahead suggestions for partially typed addresses.

When to use: As user types in address input field (typically after 3+ characters).

Critical: Always display Address.Label to users, NOT Title. The Title field may show components in reverse order and is not suitable for display.

Returns: Array of suggestions, each with:

  • PlaceId - Use this to fetch full details with GetPlace

  • Address.Label - Display this to users (e.g., "123 Main St, Seattle, WA 98101")

  • Title - DO NOT display (may be reversed: "98101, WA, Seattle, Main St, 123")

GetPlace

Purpose: Retrieve complete place details after user selects autocomplete suggestion.

When to use: When user clicks/selects an autocomplete suggestion.

Input: PlaceId from Autocomplete result.

Returns: Complete place object with nested Address structure:

{
  PlaceId: "string",
  Address: {
    Label: "123 Main St, Seattle, WA 98101, USA",
    Region: {
      Code: "WA",           // State/province code
      Name: "Washington"    // Full state name
    },
    Country: {
      Code2: "US",          // ISO 2-letter country code
      Code3: "USA",         // ISO 3-letter country code
      Name: "United States" // Full country name
    },
    Locality: "Seattle",    // City name (string)
    PostalCode: "98101",    // Postal code (string)
    Street: "Main St",      // Street name (string)
    AddressNumber: "123"    // Street number (string)
  },
  Position: [lon, lat]      // Coordinates
}

Important: Address properties are nested objects, not flat strings. Access as address.Region.Code, not address.RegionCode.

Geocode

Purpose: Resolve a complete address typed by the user (when they don't select an autocomplete suggestion) to coordinates and a matched address label.

When to use: On form submission if the user typed an address but didn't select any autocomplete suggestion.

Input: Complete address string.

Returns: Array of matching addresses with coordinates and a formatted label.

Note: Geocode is NOT postal address validation. It returns coordinates, a best-match label, and MatchScores (match confidence), but not a postal-deliverability verdict (whether an address is mailable/locatable) or standardized per-component validation status. For verifying and standardizing addresses against authoritative postal data, use the asynchronous Jobs API (StartJob with Action ValidateAddress) — see the address-verification reference.

Code Examples

Complete Implementation
// Initialize client
const authHelper = amazonLocationClient.withAPIKey(API_KEY, REGION);
const client = new amazonLocationClient.GeoPlacesClient(
  authHelper.getClientConfig(),
);

let selectedPlaceId = null;

// Stage 1: Autocomplete as user types
document
  .getElementById("address-input")
  .addEventListener("input", async (e) => {
    const query = e.target.value;

    if (query.length < 3) {
      document.getElementById("suggestions").innerHTML = "";
      return;
    }

    try {
      const command = new amazonLocationClient.places.AutocompleteCommand({
        QueryText: query,
        MaxResults: 5,
      });

      const response = await client.send(command);

      // Display suggestions using Address.Label (NOT Title!)
      const suggestionsHtml = response.ResultItems.map(
        (item) =>
          `<div class="suggestion" data-place-id="${item.Place?.PlaceId}">
        ${item.Address.Label}
      </div>`,
      ).join("");

      document.getElementById("suggestions").innerHTML = suggestionsHtml;
    } catch (error) {
      console.error("Autocomplete error:", error);
      // Show error to user
    }
  });

// Stage 2: User selects suggestion → GetPlace
document.getElementById("suggestions").addEventListener("click", async (e) => {
  if (!e.target.classList.contains("suggestion")) return;

  const placeId = e.target.dataset.placeId;
  selectedPlaceId = placeId;

  try {
    const command = new amazonLocationClient.places.GetPlaceCommand({
      PlaceId: placeId,
    });

    const response = await client.send(command);
    const place = response;

    // Populate form with complete details
    document.getElementById("address-input").value = place.Address.Label;
    document.getElementById("street").value =
      `${place.Address.AddressNumber || ""} ${place.Address.Street || ""}`.trim();
    document.getElementById("city").value = place.Address.Locality || "";
    document.getElementById("state").value = place.Address.Region?.Code || "";
    document.getElementById("zip").value = place.Address.PostalCode || "";
    document.getElementById("country").value =
      place.Address.Country?.Code2 || "";

    // Store coordinates for later use
    document.getElementById("lat").value = place.Position[1];
    document.getElementById("lon").value = place.Position[0];

    // Clear suggestions
    document.getElementById("suggestions").innerHTML = "";
  } catch (error) {
    console.error("GetPlace error:", error);
    alert("Failed to fetch address details");
  }
});

// Stage 3: User submits without selecting → Geocode (resolve to coordinates)
document.getElementById("submit").addEventListener("click", async () => {
  if (selectedPlaceId) {
    // User selected from autocomplete, proceed
    submitForm();
    return;
  }

  // User typed address without selecting; resolve it to coordinates with Geocode
  const query = document.getElementById("address-input").value;

  if (!query) {
    alert("Please enter an address");
    return;
  }

  try {
    const command = new amazonLocationClient.places.GeocodeCommand({
      QueryText: query,
      MaxResults: 1,
    });

    const response = await client.send(command);

    if (response.ResultItems.length === 0) {
      alert("Address not found. Please check and try again.");
      return;
    }

    const result = response.ResultItems[0];

    // Confirm with user if address was standardized
    if (result.Address.Label !== query) {
      const confirmed = confirm(`Did you mean: ${result.Address.Label}?`);
      if (!confirmed) return;
    }

    // Populate with geocoded result
    document.getElementById("lat").value = result.Position[1];
    document.getElementById("lon").value = result.Position[0];

    submitForm();
  } catch (error) {
    console.error("Geocode error:", error);
    alert("Failed to resolve address");
  }
});

function submitForm() {
  // Proceed with form submission
  console.log("Submitting form with resolved address");
}

Error Handling

Autocomplete Errors

  • Rate limiting: Implement debouncing (300ms delay) before calling API

  • Network failures: Show cached suggestions or friendly message

  • No results: Allow user to continue typing or submit for geocoding

GetPlace Errors

  • Invalid PlaceId: Should not happen if using autocomplete results, but handle gracefully

  • Network timeout: Retry once, then show error message

Geocode Errors

  • No results: Prompt user to check spelling or use autocomplete

  • Multiple results: Present user with options to select correct one

  • Ambiguous address: Ask for more details (e.g., city/state)

Best Practices

Performance

  • Debounce autocomplete: Wait 300ms after user stops typing before API call

  • Cancel previous requests: Cancel in-flight autocomplete requests when new input arrives

  • Cache results: Cache autocomplete results for repeated queries

User Experience

  • Always use Address.Label: Never display the Title field - it may be reversed

  • Show visual feedback: Loading indicators during API calls

  • Keyboard navigation: Allow arrow keys and Enter to navigate suggestions

  • Clear affordances: Make it obvious when an address suggestion has been selected or resolved

Data Handling

  • Store PlaceId: Keep PlaceId with address for future reference

  • Store coordinates: Save Position for mapping and distance calculations

  • Handle missing fields: Not all addresses have all components (e.g., AddressNumber)

  • Respect nested structure: Access address.Region.Code, not address.RegionCode

Accessibility

  • ARIA labels: Use proper ARIA attributes for autocomplete

  • Keyboard support: Full keyboard navigation for suggestions

  • Screen reader announcements: Announce number of suggestions found

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an MCP server, Needs an API key

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
aws-geospatial
Publisher
AWS Labs (Official)
Distributed by
AWS Labs
Source
awslabs/agent-plugins · plugins/amazon-location-service/skills/amazon-location-service · commit fbefb37
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • NOTICE (added by AutoGineer from NOTICE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by aws-geospatial or AWS Labs.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download amazon-location-service.zip