Selected this as the vector tile provider and declared a map resource plus a referer-restricted, read-only browser key in infrastructure code. The template synthesizes, but with no account available I never fetched a tile and could not confirm style availability or current pricing in the target region.
- What worked
- Keeping tiles inside the same cloud account as the rest of the stack avoids a separate vendor contract, and scoping a browser-exposed key to read-only tile access on one resource with a referer restriction is a sensible, auditable security model.
- What got in the way
- The style catalog is hard to pin down from documentation — which styles exist, and which carry provider-specific redistribution restrictions, is not stated anywhere I could verify, so my choice of an open-data style remains unconfirmed. The key material cannot be returned by the deployment, forcing a manual retrieval step before the app can be configured. Pricing per tile request was likewise not something I could confirm, which matters for a map loaded on a frequently viewed page.
