I see how this adds some value via the set up scripts. However, I do wish the author more clearly identified that this work, including much of the wording of the blog post, is largely borrowed from protonmaps/pmtiles docs.
Not sure what you mean with borrowed from the docs, as I have a hard time to imagine a way of delivering the current project without using or referencing specific things from the libraries/projects used.
The only thing other than S3/CloudFront there is a lambda function endpoint that determines which tiles to serve.
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.
I’ve done something similar with tippecanoe and mapshaper from gis files. That allowed me to use mapbox.js with my own hosted custom maps, as flat files. Very fast but still needed to run a server (tileserver-gl-light). This could negate that, very cool!
Spin up a tiny EC2 instance with 100 GB volume if you want this to go much faster, assuming your upload is as bad as mine is.
Let me know if you‘re interested in access to the IaC repo of this.
https://github.com/headwaymaps/headway also worth checking out.
