PMTiles on Lambda

Generates a Lambda function for deploying PMTiles on Lambda behind Lambda Function URLs or API Gateway. (CloudFront is recommended as a cache in front.)

The Content-Type header of responses will be application/vnd.mapbox-vector-tile : this is one of the CloudFront compressible types.

How To Use

Self-contained Lambda ZIP:

protomaps.github.io/PMTiles/lambda_function.zip

(On Safari, right click -> Download Linked File... will keep the ZIP intact)

Building the Lambda ZIP yourself:

npm run build

Upload the resulting dist/lambda_function.zip using the Lambda console or paste dist/index.js.

Configure these Lambda environment variables:

BUCKET: the S3 bucket name.
PMTILES_PATH: optional, define how a tileset name is translated into an S3 key. Default {name}.pmtiles
- Example path setting for objects in a directory: my_folder/{name}/file.pmtiles
TILE_PATH: optional, define the URL route of the tiles API. Default /{name}/{z}/{x}/{y}.pbf
CORS: optional, set the value of the Access-Control-Allow-Origin response header. Examples: https://example.com, *. Only supports one origin, so useful for development or staging environments only. For production use you should use CloudFront CORS configuration.

Test Event

Lambda Function URLs:

{
  "rawPath": "/my-tileset-name/0/0/0.mvt"
}

API Gateway (HTTP or REST):

{
  "pathParameters": {
   "proxy": "my-tileset-name/0/0/0.mvt"
  }
}

Monitoring

TBD

Lambda@Edge

Lambda@Edge's multi-region features have little benefit when fetching data from S3 in a single region, and Lambda@Edge doesn't support environment variables or responses over 1 MB. For globally distributed caching, use CloudFront in combination with Lambda Function URLs.

API Gateway

your Lambda Proxy Integration route will need to specify a greedy capturing parameter called proxy e.g. /{proxy+} (the default).
API Gateway responses will always be GZIP-encoded, to work around binary content detection problems.

2.3 KiB Raw Blame History