The architecture diagram in the repo is a little overwhelming for a Friday night — conceivably you could just toss a public pmtiles file on s3, and access it directly from the maplibre front-end, right? (As long as you’re not worried about someone coming along and downloading your whole tileset)
The architecture mostly is just putting things in S3 and serving them on a CDN. The diagram just goes into detail because little things like permissions and response header settings exist as separate but related "Policy" resources at the AWS level.
The only thing other than S3/CloudFront there is a lambda function endpoint that determines which tiles to serve.
Comments
The architecture diagram in the repo is a little overwhelming for a Friday night — conceivably you could just toss a public pmtiles file on s3, and access it directly from the maplibre front-end, right? (As long as you’re not worried about someone coming along and downloading your whole tileset)
The architecture mostly is just putting things in S3 and serving them on a CDN. The diagram just goes into detail because little things like permissions and response header settings exist as separate but related "Policy" resources at the AWS level.
The only thing other than S3/CloudFront there is a lambda function endpoint that determines which tiles to serve.
Right, the diagram is generated from the IaC of the project itself, so it contains all AWS resources involved.
You could use the Lambda function to verify Access Tokens etc. before returning the tile data if that is a concern.
CloudFront as CDN will enable Edge caching, meaning that recurrent requests will serve much faster, as S3 is always region-based.