Cloud Storage Platforms for PMTiles

PMTiles is designed to work on any S3-compatible cloud storage platform that supports HTTP Range Requests. Proper support for Cross-Origin Resource Sharing is required if your map frontend is hosted on a different domain than your storage platform.

• Most cloud storage platforms support moderate-size uploads through a web interface.

• The pmtiles command line tool has a pmtiles upload command for moving files to cloud storage. This requires credentials with your specific platform.

• RClone is another recommended tool for managing large files on S3-compatible storage.

rclone copyto my-filename my-configuration:my-bucket/my-folder/my-filename.pmtiles --progress --s3-chunk-size=256M

• The aws command-line tool can be used for uploads, as well as setting CORS configuration on any S3-compatible platform.

R2 is the recommended storage platform for PMTiles because it does not have bandwidth fees, only per-request fees: see R2 Pricing.

• R2 supports HTTP/2.

• R2 CORS must be configured through a command-line utility like the aws tool:

{
  "CORSRules": [
    {
      "AllowedOrigins": ["https://example.com"],
      "AllowedHeaders": ["range"],
      "AllowedMethods": ["GET","HEAD"],
      "MaxAgeSeconds": 3000,
      "ExposeHeaders": ["ETag"]
    }
  ]
}

Example of using the aws command line tool to configure R2 CORS:

aws s3api put-bucket-cors --bucket MY_BUCKET --cors-configuration file:///home/user/cors_rules.json --endpoint-url https://S3_COMPATIBLE_ENDPOINT

• only HTTP/1.1 supported

• From your S3 Bucket's "Permissions" tab, scroll to the Cross-origin resource sharing (CORS) editor.

S3 Policy for public reads:

{
    "Version": "2012-10-17",
    "Id": "",
    "Statement": [
        {
            "Sid": "PublicRead",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::example-bucket/*"
        }
    ]
}

S3 CORS Configuration:

[
    {
        "AllowedHeaders": ["Range"],
        "AllowedMethods": ["GET","HEAD"],
        "AllowedOrigins": ["https://example.com"],
        "ExposeHeaders": ["ETag"]
    }
]

• HTTP/2 supported

• See the Cloud Storage CORS documentation

• Install the gsutil tool to set CORS headers

[
    {
      "origin": ["https://example.com"],
      "method": ["GET","HEAD"],
      "responseHeader": ["range","etag"],
      "maxAgeSeconds": 300
    }
]

gsutil cors set google_cloud_cors.json gs://my-bucket-name

• only HTTP/1.1 supported

• Configuration through Web Portal

• CORS Configuration - in left sidebar Resource Sharing (CORS)

  • Set Allowed Headers to Range
  • Set Exposed Headers to range,accept-ranges,etag

• only HTTP/1.1 supported (even with CDN enabled)

• CORS is configured via Web UI.

• use S3Cmd config to expose ETag header

• Backblaze B2 only supports HTTP/1.1.

• Download the b2 command line utility for advanced CORS settings or use the Bucket web UI for simple settings

• See B2 CORS Rules

Sample CORS Configuration:

[
    {
      "corsRuleName": "allowHeaders",
      "allowedOrigins": ["https://example.com"],
      "allowedOperations":["b2_download_file_by_name"],
      "allowedHeaders": ["range"],
      "maxAgeSeconds": 300
    }
]

GitHub pages supports repositories up to 1 GB. If your PMTiles file fits, it's an easy way to host.

Scaleway Object Storage only supports HTTP/1.1.

• Nginx supports HTTP Range Requests. CORS headers should be set by configuration files.

• Caddy has known issues with serving large (> 5 GB) archives to particular browsers and is not officially supported right now.

• Accelerate your maps and serve from private buckets with CDN integration.
• Learn how to customize your map's Basemap Layers.